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/implementnpx skills add blake-simpson/belmont --skill implementgit clone --depth 1 https://github.com/blake-simpson/belmontWhat 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.00015 | $0.11463 |
| Opus 5 | $0.00008 | $0.05731 |
| Sonnet 5 | $0.00003 | $0.02293 |
| Haiku 4.5 | $0.00002 | $0.01146 |
Grade A, and why
implement scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **Never curl, probe, or assume `localhost:3000`** (or any other well-known default) is "yours". A port that's already bound from outside your worktree belongs to someone else — another worktree, the user's own dev ses How it starts
The opening of the file, as written. The whole thing — 597 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Belmont: Implement
You are the implementation orchestrator. Your job is to implement the next pending milestone from the PRD by creating a focused MILESTONE file and executing tasks through a structured agent pipeline.
Feature Selection
Belmont organizes work into features — each feature gets its own directory under .belmont/features/<slug>/ with its own PRD, PROGRESS, TECH_PLAN, and MILESTONE files.
Select the Active Feature
- List all feature directories under
.belmont/features/ - If features exist: read each feature's
PRD.mdfor its name and status, then Ask which feature to implement, or auto-select the one with pending tasks - If no features exist: tell the user to run
/belmont:product-planto create their first feature, then stop - Set the base path to
.belmont/features/<selected-slug>/
Base Path Convention
Once the base path is resolved, use {base} as shorthand:
{base}/PRD.md— the feature PRD{base}/PROGRESS.md— the feature progress tracker{base}/TECH_PLAN.md— the feature tech plan{base}/MILESTONE.md— the active milestone file{base}/MILESTONE-*.done.md— archived milestones{base}/NOTES.md— learnings and discoveries from previous sessions
Master files (always at .belmont/ root):
.belmont/PR_FAQ.md— strategic PR/FAQ document.belmont/PRD.md— master PRD (feature catalog).belmont/PROGRESS.md— master progress tracking (feature summary table).belmont/TECH_PLAN.md— master tech plan (cross-cutting architecture)
Worktree Environment
If the environment variable BELMONT_WORKTREE is set to 1, you are running in an isolated git worktree for parallel execution. Several sibling worktrees may be running the same project concurrently on different ports. Ignoring the port rules below will cause silent merge conflicts, verification flakes, and processes killing each other — treat this section as load-bearing.
Port variables set for you
Belmont populates these before your process starts. Use them directly; do not guess at port numbers, and do not copy ports out of package.json or config files.
What ships with it
2 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.
- 2d ago First seen · 597 lines · 15 tokens per session scan A 6ddc389c46a5
implement is a skill published in the GitHub repository blake-simpson/belmont (4 stars, last pushed 14d ago), licensed Apache-2.0. It adds 15 tokens to every session and 11,463 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agent-performance-benchmarker
Agent skill for performance-benchmarker - invoke with $agent-performance-benchmarker.
agent-quorum-manager
Agent skill for quorum-manager - invoke with $agent-quorum-manager.
agent-agent
Agent skill for agent - invoke with $agent-agent.
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
agent-adaptive-coordinator
Agent skill for adaptive-coordinator - invoke with $agent-adaptive-coordinator.
agent-benchmark-suite
Agent skill for benchmark-suite - invoke with $agent-benchmark-suite.