document-project

A codebase analysis tool for older or already-built projects. It examines the code, system structure, and recurring patterns to create reference documentation for coding agents.

In plain words
What is it for?
Use it to document an existing application, explain its architecture, and record coding patterns that agents should follow.
Why use it?
It gives an agent a clear picture of an unfamiliar project before changes are made. This reduces the need to reconstruct the project’s design from scattered files.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/terryso/autoqa-agent/document-project
Clone the repo
git clone --depth 1 https://github.com/terryso/AutoQA-Agent

Made for: Claude Code.

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 180 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 80% copy Near-identical to another mod in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00180
Opus 5 $0.00013 $0.00090
Sonnet 5 $0.00005 $0.00036
Haiku 4.5 $0.00003 $0.00018

Measured 2d ago against content hash 4c1e6a3f1d53, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

document-project 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.

Origin

This is a copy

80% identical to correct-course — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/bmad/bmm/workflows/document-project.md · 14 lines

What it actually says

IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:

Changes

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.

  1. 2d ago First seen · 14 lines · 25 tokens per session scan A 4c1e6a3f1d53

Subscribe to this mod's changes

document-project is a command published in the GitHub repository terryso/AutoQA-Agent (134 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 180 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to correct-course, differing in 6 lines, and is treated as a copy.