Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/edwardangert/docs-agent-plugin/setup-sitegit clone --depth 1 https://github.com/EdwardAngert/docs-agent-pluginWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00025 | $0.00826 |
| Opus 5 | $0.00013 | $0.00413 |
| Sonnet 5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
setup-site scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up the Docs Site
Turn the metadata the plugin already maintains into a navigable docs site.
The docs carry rich structure (frontmatter content types and descriptions, llms.txt in reader-priority order), but nothing turned that structure into navigation.
This command does, and nothing more: it is deliberately not a site builder.
It generates navigation from metadata, scaffolds a minimal generator setup when none exists, and leaves theming, hosting, and customization to the team.
The optional argument ($ARGUMENTS) names a generator to skip the selection question.
Process
1. Detect What Exists
- Look for an existing static site generator:
docusaurus.config.*,mkdocs.yml,astro.config.*,_config.yml(Jekyll),config.toml/hugo.toml(Hugo). - Read
.docs-assist/config.ymlfordocs_dir, andllms.txtfor the docs map. A missing or stalellms.txtis a blocker worth fixing first: offer/docs-assist:agent-ready, since the map is the navigation source (see${CLAUDE_PLUGIN_ROOT}/skills/docs-assist/reference/llms-txt.md).
2. Scaffold Only When Nothing Exists
When no generator is present, offer one, using $ARGUMENTS if given:
- Docusaurus: the richer default for product docs. Scaffold the minimal config wired to
docs_dir, no theme customization. - MkDocs: the lighter default. Scaffold a minimal
mkdocs.ymlwired todocs_dir.
Keep the scaffold small enough to read in one sitting. If a generator this command does not scaffold is already present (Astro, Hugo, Jekyll), skip to navigation and adapt to its format where the mapping is unambiguous; say plainly what you cannot generate for it.
3. Generate Navigation From the Metadata
The metadata is the source of truth; the navigation is derived, never hand-invented here.
- Order comes from
llms.txt: its reader-priority order becomes the sidebar order, and its sections become navigation groups. - Labels come from frontmatter:
titlefor the label,descriptionwhere the generator supports hover or index text. - Write the generator's navigation format:
sidebars.jsfor Docusaurus, thenavblock inmkdocs.ymlfor MkDocs. - Never silently overwrite navigation someone curated. If a sidebar or nav block exists, show the diff and confirm. Preserve entries for pages outside the docs set.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 53 lines · 25 tokens per session scan A 3c5fa1701989
setup-site is a command published in the GitHub repository EdwardAngert/docs-agent-plugin (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 826 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.