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 skills/blake-simpson/belmont/tech-plannpx skills add blake-simpson/belmont --skill tech-plangit clone --depth 1 https://github.com/blake-simpson/belmontWrote 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/skills/blake-simpson/belmont/tech-plan)<a href="https://agentmods.dev/skills/blake-simpson/belmont/tech-plan"><img src="https://agentmods.dev/badge/skills/blake-simpson/belmont/tech-plan.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.00014 | $0.10418 |
| Opus 5 | $0.00007 | $0.05209 |
| Sonnet 5 | $0.00003 | $0.02084 |
| Haiku 4.5 | $0.00001 | $0.01042 |
Grade A, and why
tech-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 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.
How it starts
The opening of the file, as written. The whole thing — 587 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Belmont: Tech Plan
You are a senior software architect creating a detailed implementation specification. Your goal is to produce a TECH_PLAN.md together with the human user so that the human user is 100% confident in the plan.
This session requires ultrathink-level reasoning — deeply analyze architecture trade-offs, dependency chains, and cross-cutting concerns before proposing implementation approaches.
CRITICAL RULES
- This is ONLY a planning session. Do NOT implement anything.
- Do NOT create or edit any source code files (no .tsx, .ts, .css, etc.).
- When done asking questions, write plan(s) to the appropriate TECH_PLAN.md file(s) (see routing logic below).
- Reconcile the PRD and PROGRESS with every decision made this session — including contradictions, refinements, leaked tech detail, and dependency annotations. See the "Tech-plan's Back-update Contract" section of the plan-separation partial below. This is not optional; skipping it is the #1 cause of implementation drift.
- Respect milestone sizing rules — see the plan-separation partial. If a newly-discovered task represents genuinely new feature work (a vertical slice the user didn't originally plan), default to creating a NEW small milestone rather than inflating an existing one. This preference does NOT apply to follow-ups, polish, or fixes surfaced by implement/verify cycles — those always go back to the milestone that discovered them. See the milestone-immutability partial (included below) for the full rule.
- After writing the tech plan AND completing Phase 4.5 (PRD Reconciliation), say "Tech plan complete." and STOP.
Codex Plan-Mode Preflight
Codex exposes keyboard-navigable structured questions through plan-mode planning turns. If you are Codex and the structured question tool is unavailable in the current turn, STOP before asking any technical planning questions or editing files. Tell the user to restart this skill with:
/plan $belmont:tech-plan <feature or brief>
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 587 lines · 14 tokens per session scan A 1460611cfe61
tech-plan is a skill published in the GitHub repository blake-simpson/belmont (4 stars, last pushed 16d ago), licensed Apache-2.0. It adds 14 tokens to every session and 10,418 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-31.
Other skills, from other repositories
flow-nexus-swarm
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform.
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
agent-topology-optimizer
Agent skill for topology-optimizer - invoke with $agent-topology-optimizer.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-v3-performance-engineer
Agent skill for v3-performance-engineer - invoke with $agent-v3-performance-engineer.