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/hulupeep/specflow/readme-auditgit clone --depth 1 https://github.com/Hulupeep/SpecflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/hulupeep/specflow/readme-audit)<a href="https://agentmods.dev/commands/hulupeep/specflow/readme-audit"><img src="https://agentmods.dev/badge/commands/hulupeep/specflow/readme-audit.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00905 |
| Opus 5 | $0.00000 | $0.00452 |
| Sonnet 5 | $0.00000 | $0.00181 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
readme-audit 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 6d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README Audit
Audit a README's reading flow by treating it as a conversion funnel. Every section is
evaluated against a target reader and a terminal action. Produces a structured audit
blueprint that feeds directly into /readme-restructure.
Before Starting
Establish three things (ask if not provided):
- Target reader(s) — who arrives at the document? If two types, identify the conversion event (e.g. "evaluator becomes implementor")
- Terminal action — what should the reader be able to DO after reading? Must be concrete and specific.
- README path — which file to audit
Process
Step 1: Map the Document
Read the entire README. Create a section inventory: title, line range, one-sentence description. Flag any sections that duplicate content elsewhere in the document.
Step 2: Audit Each Section
For every section, produce a row:
| # | Section | Lines | Reader Q Answered | Mental State IN → OUT | Content | Flow | Classification |
|---|
Reader Q Answered: What question is the reader asking when they arrive here? If it answers a question they haven't asked yet, it is mispositioned.
Mental State IN → OUT: Short phrase. E.g. "curious → convinced" or "ready to install → confused by options"
Content (0.0–1.0): Correct, appropriate density, right detail level for this reader at this moment?
Flow (0.0–1.0): Does this section hand the reader off cleanly to the next? Does the reader know where to go next and why?
Classification:
KEEP— right content, right location, right densityKEEP-SHORTEN— right location but too long; trim to one line with a linkPROMOTE— good content, wrong location; becomes its own linked docPROMOTE-MERGE— good content that should merge with another promoted sectionREORDER— right content, wrong position in the flowCUT— serves neither reader type at any positionDUPLICATE— repeats another section; one instance kept, rest cut
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.
- 6d ago First seen · 99 lines · 0 tokens per session scan A c745c585ea60
readme-audit is a command published in the GitHub repository Hulupeep/Specflow (25 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 905 tokens. 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-30.
Other commands, from other repositories
review-impl
Unbiased review of another session's implementation (diff, staged, or branch).
re-review
Round 2+ review — confirm revisions landed, catch regressions, do not re-litigate.
review-plan
Unbiased review of another session's implementation plan.
review-spec
Unbiased review of another session's spec or design doc.
fix
Auto-fix archguardian findings (unused imports, naming violations).
baseline
Create or update an archguardian baseline for incremental adoption.