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/evan043/claude-cli-advanced-starter-pack/feature-audit.templategit clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/evan043/claude-cli-advanced-starter-pack/feature-audit.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/feature-audit.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/feature-audit.template.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.02138 |
| Opus 5 | $0.00000 | $0.01069 |
| Sonnet 5 | $0.00000 | $0.00428 |
| Haiku 4.5 | $0.00000 | $0.00214 |
Grade A, and why
feature-audit.template 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: Full-stack feature truth verification - audit what was actually built vs what was planned options:
- label: "Full Audit" description: "Verify all features against the codebase with truth table, confidence, and gaps"
- label: "Gaps Only" description: "Show only gaps - recently completed but untested or low-confidence features"
- label: "Generate Tests" description: "Auto-generate missing Playwright smoke tests and backend contract tests"
- label: "Dashboard" description: "Run audit then open Feature Truth tab in the site-intel dashboard"
Feature Audit - Full-Stack Truth Verification
Verify what was ACTUALLY built against what was PLANNED. Maps the CCASP planning hierarchy (Epic → Roadmap → Phase → Task) to verifiable features and checks 6 truth dimensions per feature.
Arguments
/feature-audit— Full audit (default: Full Audit)/feature-audit --feature "auth"— Audit a single feature by name/feature-audit --gaps-only— Show only gaps (recently completed but untested)/feature-audit --generate-tests— Auto-generate missing smoke + contract tests/feature-audit --dashboard— Run audit then open dashboard to Feature Truth tab/feature-audit --roadmap <slug>— Filter to specific roadmap
What It Verifies (6 Truth Dimensions)
| Dimension | Points | What It Checks |
|---|---|---|
| UI Exists | 20 | Route in catalog + component file on disk |
| Backend Exists | 20 | API endpoint in backend routers |
| API Wired | 20 | Frontend code references backend endpoint |
| Data Persists | 15 | Database model/migration exists |
| Permissions | 15 | Auth middleware on endpoint |
| Error Handling | 15 | Error boundaries, try-catch, error toasts |
| Smoke Test | +5 | Existing Playwright test covers this feature |
| Contract Test | +5 | Existing backend contract test covers this API |
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 · 210 lines · 0 tokens per session scan A 7cc73d42947d
feature-audit.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,138 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
template
Manage issue templates for streamlined issue creation.
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
release-harn
Run the tag-first Harn release workflow.
discover
Search the Everruns(Dev) API catalog for available operations.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.