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/0xuxdesign/ai-codebase-boilerplate/plangit clone --depth 1 https://github.com/0xUXDesign/ai-codebase-boilerplateWhat 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 | $0.00010 | $0.00182 |
| Opus 5 | $0.00005 | $0.00091 |
| Sonnet 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 3d 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.
- 3d 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 5mo ago), licensed MIT. It adds 10 tokens to every session and 182 once invoked, about $0.0001 per session on Opus 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
tailtest
Generate or update tests for $ARGUMENTS.
summary
Show a summary of this tailtest session.
tailtest-off
Pause tailtest for this session.
deploy
Command "deploy" from PraveenJayaprakash-JP/repomemory, covering deployment workflow, 1. pre-deploy checks, 2. build verification, 3. environment validation and 4. deployment steps (platform detection).
diagnose
Command "diagnose" from Vimalk0703/shipworthy, covering process, example output, project diagnosis report, critical (fix immediately) and high (fix soon).
validate
Command "validate" from Vimalk0703/shipworthy, covering /validate — pre-push validation gate, what this does, steps, when to run and output format.