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/rtazima/claude-proj-blueprint/deploygit clone --depth 1 https://github.com/rtazima/claude-proj-blueprintWrote 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/rtazima/claude-proj-blueprint/deploy)<a href="https://agentmods.dev/commands/rtazima/claude-proj-blueprint/deploy"><img src="https://agentmods.dev/badge/commands/rtazima/claude-proj-blueprint/deploy.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 | $0.00000 | $0.00138 |
| Opus 5 | $0.00000 | $0.00069 |
| Sonnet 5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
deploy 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 4d 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
Run the project deploy checklist.
Workflow:
- Run tests: [SPEC] test command
- Run lint: [SPEC] lint command
- Check for exposed secrets:
grep -r "API_KEY\|SECRET\|PASSWORD" src/ --include="*.py" --include="*.ts" --include="*.tsx" - Check for pending migrations
- List changes since last tag:
git log $(git describe --tags --abbrev=0)..HEAD --oneline - Generate change summary for release notes
If any step fails, stop and report the problem.
See docs/runbooks/deploy.md for specific procedures.
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.
- 4d ago First seen · 13 lines · 0 tokens per session scan A 88fa416004d1
deploy is a command published in the GitHub repository rtazima/claude-proj-blueprint (20 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 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
spec-release
Generate release notes, changelog, and deployment checklist.
spec-complete
Run full post-completion pipeline (accept, docs, release, retro).
ship
Deliver the increment. Then go live with a rollback you have run.
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
release
Orchestrate a complete release workflow with quality gates, version bumping, and publishing automation.
release
Walk the llmwiki release process step by step.