Back to directory

llmdoc

Persistent engineering context for coding agents, so an agent retrieves only the decisions, constraints and cross-module contracts a task needs, verifies them against the live repository, and rechecks them as code evolves instead of rereading everything each session.

llmdoc

llmdoc stores durable engineering meaning, not a copy of the repository, under a llmdoc/ directory; an agent first retrieves the smallest useful knowledge set for a task, uses the source and tests to confirm current facts, and later verifies affected knowledge as a review obligation, without automatically rewriting documentation on every code change.

For Claude Code, it installs as a plugin through /plugin marketplace add and /plugin install, then initializes a repository with an /llmdoc:init skill; for Codex, it adds through codex plugin marketplace add and the /plugins panel, then runs the same init skill from a prompt. A repository that already has an llmdoc/ directory can be queried directly with npx -y @tokenroll/llmdoc tree or search, without installing the plugin.

The external @tokenroll/llmdoc package should not be added to a consuming project's own package.json or lockfile, and pinning a version with npx -y @tokenroll/llmdoc@ is recommended for reproducible runs. It is written in TypeScript and needs Node.js 18 or newer and a Git repository.

More in Agent skills

See all 581
  • Provenance gate

    github.com

    A deterministic authorization gateway that sits between an AI agent and its tools, tracing where each parameter of a side-effect call came from, and blocking the call or asking a human when the source does not check out.

  • A markdown framework of system rules that restates Isaac Asimov's Four Laws of Robotics as a set of prioritized loss calculations for large-language-model agents to follow, published as a discovery file for agents and crawlers to read.

  • Vitruvius

    github.com

    An engineering research agent that runs a discover, read, synthesize, verify and review loop over technical questions, reading sources directly rather than inferring from titles, and publishing its own scored verifier benchmark, weaknesses included.