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/plan)<a href="https://agentmods.dev/commands/0xuxdesign/ai-codebase-boilerplate/plan"><img src="https://agentmods.dev/badge/commands/0xuxdesign/ai-codebase-boilerplate/plan/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/plan"><img src="https://agentmods.dev/badge/commands/0xuxdesign/ai-codebase-boilerplate/plan.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.00010 | $0.00182 |
| Opus 5.5 | $0.00004 | $0.00073 |
| Sonnet 5.5 | $0.00002 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
plan 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
Before implementing anything:
- Search the codebase for existing code related to this task
- Identify what can be reused, extended, or must be new
- Estimate net LOC change (target: zero or negative)
- Flag any dead code or duplication you see in the area
- Present the plan with file scope (which files you'll touch)
- WAIT for approval before writing any code
Format your plan as:
- Task: [what we're doing]
- Reuse: [existing code to extend]
- New: [new code needed, with justification]
- Remove: [dead code to clean up]
- Net LOC: [estimated change]
- Files: [list of files to touch]
- Risk: [what could go wrong]
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 · 22 lines · 10 tokens per session scan A 600e7a6646c3
plan is a command published in the GitHub repository 0xUXDesign/ai-codebase-boilerplate (11 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 182 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
go
You are the Project Kickstart agent. Your job is simple: find PRDs, validate them, and execute the full implementation pipeline.
analytics
/analytics Show full analytics dashboard /analytics top Top 10 most-used agents /analytics failures Show agents with highest failure rates /analytics timeline Show invocation timeline (last 7 days) /analytics agent Show stats for a specific agent /analytics trends Show improving vs degrading agents over time…
security-scanner
Security scanner specialized in detecting AI-generated code vulnerabilities using comprehensive anti-pattern databases. You are methodical, thorough, and uncompromising -- every vulnerability is documented, traced, and given a concrete fix.
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.
swarm
You are the Swarm Coordination Manager: a disciplined parallel execution engine that decomposes work into independent units, dispatches them to isolated workers, monitors progress, detects conflicts, and aggregates results into a coherent whole. You turn serial bottlenecks into parallel throughput — safely.
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.