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.
git clone --depth 1 https://github.com/0xUXDesign/ai-codebase-boilerplateWrote 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/0xuxdesign/ai-codebase-boilerplate/audit-tests)<a href="https://agentmods.dev/commands/0xuxdesign/ai-codebase-boilerplate/audit-tests"><img src="https://agentmods.dev/badge/commands/0xuxdesign/ai-codebase-boilerplate/audit-tests/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/0xuxdesign/ai-codebase-boilerplate/audit-tests"><img src="https://agentmods.dev/badge/commands/0xuxdesign/ai-codebase-boilerplate/audit-tests.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.00194 |
| Opus 5.5 | $0.00005 | $0.00078 |
| Sonnet 5.5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
audit-tests 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 1mo 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.
What it actually says
For the specified directory (or all tests if none specified):
- List every test file and test count
- Classify each test as:
- CRITICAL — tests a core business behavior, uses hardcoded expected values
- USEFUL — tests a real edge case or integration boundary
- REDUNDANT — duplicates coverage of another test
- TAUTOLOGICAL — asserts only
.toBeDefined(),.toBeTruthy(), or computes expected values from the same code it's testing - ORPHANED — tests code that no longer exists
- OVER-MOCKED — mocks so much the test is self-referential
- Recommend: KEEP / CONSOLIDATE / DELETE for each
- REPORT ONLY — do NOT modify or delete any tests
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.
- 1mo ago First seen · 17 lines · 12 tokens per session scan A e341a96d7962
audit-tests is a command published in the GitHub repository 0xUXDesign/ai-codebase-boilerplate (11 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 194 once invoked, about $0.0000 per session on Opus 5.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-30.
Other commands, from other repositories
forge
/forge Full Forge pipeline (semi-auto + parallel) /forge [prd-file] Forge a specific PRD /forge --blitz Forge with TDD enforcement.
feature
Role: Per-feature quality pipeline that takes a story or feature description from zero to a committed, documented, tested, and evaluated implementation. No stage is skipped. No commit happens without the evaluator's approval.
gate-keeper
Role: Guardian that stands between stages of development and permits passage only when capability is demonstrated through irrefutable evidence.
tester
You are an exacting senior software tester — a quality gatekeeper who assumes code fails until proven otherwise. You find the failure cases others miss, never accept vague assurances, and never let gaps in test coverage slide.
anvil
/anvil Run all tiers on current story/changed files /anvil a1 Tier A1 only (shell checks: syntax, patterns, imports, SAST) /anvil a1 Tier A1 on specific file /anvil a2 Tier A2 (canary smoke test) /anvil a3 Tier A3 (self-adversarial review of last implementation) /anvil a4 Tier A4 (scope validation + Semgrep SAST deep…
refactor
You are the Refactor Specialist, a rigorous code quality engineer who improves code structure, maintainability, and performance while preserving behavior. You never break working code - you make it better.