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/bravew/trove/docgit clone --depth 1 https://github.com/bravew/troveWhat 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.00009 | $0.00846 |
| Opus 5 | $0.00005 | $0.00423 |
| Sonnet 5 | $0.00002 | $0.00169 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
doc 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 2d ago.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Generator
You are a documentation sync tool. Your job is to keep docs/ in sync with the actual codebase.
Arguments
The user may pass an argument: $ARGUMENTS
| Argument | Action |
|---|---|
| (empty/default) | Sync all docs — run check first, then update stale sections in priority order |
check |
Report what's stale without changing anything |
architecture |
Regenerate architecture documentation only |
api |
Regenerate API/endpoint documentation only |
components |
Regenerate component/module documentation only |
routes |
Regenerate routing documentation only |
Process
Step 0: Detect Project Type
Determine the project stack from config files to know what source files to check:
| Stack | Config File | Typical Source Dirs |
|---|---|---|
| Python/FastAPI | pyproject.toml |
src/, app/ |
| React/Vue | package.json |
src/components/, src/routes/, src/hooks/ |
| Next.js | next.config.* |
app/, pages/, components/ |
| Swift | Package.swift |
Sources/, Tests/ |
For check mode:
- Check what source files changed recently:
git log --since='2 weeks ago' --name-only --pretty=format: -- src/ app/ | sort -u - For each doc ↔ source pair, count entities in both and diff:
- Architecture docs — check module/class/component counts vs doc
- API docs — check route/endpoint counts vs doc
- Component docs — check component/hook/store counts vs doc
- Output a status table:
| Document | Status | Details | |----------|--------|---------| | architecture.md | STALE | 2 new modules not documented | | endpoints.md | CURRENT | — |
For default sync (no argument):
- Run the
checkprocess first - Update stale sections one at a time, in this priority order:
- Architecture — highest impact for understanding
- API/endpoints — reference material
- Components/modules — only if source changed
- Use
Agentsubagents to read source code in parallel when multiple sections need updating - After all updates, output a summary of what changed
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.
- 2d ago First seen · 91 lines · 9 tokens per session scan A a68f14079b7a
doc is a command published in the GitHub repository bravew/trove (10 stars, last pushed 3d ago), licensed MIT. It adds 9 tokens to every session and 846 once invoked, about $0.0000 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.