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/codex-plan-applynpx skills add blake-simpson/belmont --skill codex-plan-applygit 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/codex-plan-apply)<a href="https://agentmods.dev/skills/blake-simpson/belmont/codex-plan-apply"><img src="https://agentmods.dev/badge/skills/blake-simpson/belmont/codex-plan-apply.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.00045 | $0.00768 |
| Opus 5 | $0.00023 | $0.00384 |
| Sonnet 5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
codex-plan-apply 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Belmont: Codex Plan Apply
Use this skill only when the user provides a BELMONT_PLAN_PACKET produced by a Codex plan-mode Belmont planning session.
This is a Codex compatibility adapter. Other agents that can ask structured questions and write files in the same session should keep using product-plan and tech-plan directly.
Purpose
Codex plan mode provides keyboard-navigable structured questions, but may not be the right phase for writing planning files. This skill runs after the user leaves plan mode. It persists the already-approved planning output without reopening the interview.
Rules
- Do NOT ask product or technical planning questions.
- Do NOT infer missing PRD, PROGRESS, TECH_PLAN, or models.yaml content.
- Do NOT edit source code.
- Only write files under
.belmont/. - Only write, create, or update files explicitly listed in the packet.
- Preserve existing content unless the packet explicitly says a file should be replaced.
- For update operations, edit the named sections only. Never replace a real existing file unless the packet explicitly marks it as a full-file replacement.
- If the packet is incomplete, ambiguous, malformed, or lacks target paths, stop and ask the user to rerun the relevant Codex plan-mode skill.
Expected Packet Shape
The packet is plain Markdown in a fenced block:
```BELMONT_PLAN_PACKET
kind: product-plan | tech-plan
mode: create | update
feature_slug: <slug or none>
base_path: .belmont/features/<slug> | .belmont
files:
- path: .belmont/features/<slug>/PRD.md
operation: create | replace | update-section
content: |
...
- path: .belmont/features/<slug>/PROGRESS.md
operation: create | replace | update-section
content: |
...
post_apply:
commit_message: belmont: update planning files after product planning
next_prompt: /plan $belmont:tech-plan <feature>
```
YAML-like structure is preferred, but exact YAML parsing is not required. The key requirement is that each file path, operation, and content block is explicit enough to apply safely.
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 · 85 lines · 45 tokens per session scan A 1d46e1852596
codex-plan-apply is a skill published in the GitHub repository blake-simpson/belmont (4 stars, last pushed 16d ago), licensed Apache-2.0. It adds 45 tokens to every session and 768 once invoked, about $0.0002 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
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…
image-generation
Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.
podcast-generation
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
bootstrap
Generate a personalized SOUL.md through a warm, adaptive onboarding conversation. Trigger when the user wants to create, set up, or initialize their AI partner's identity — e.g., "create my SOUL.md", "bootstrap my agent", "set up my AI partner", "define who you are", "let's do onboarding", "personalize this AI", "make…
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.