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/statusnpx skills add blake-simpson/belmont --skill statusgit 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/status)<a href="https://agentmods.dev/skills/blake-simpson/belmont/status"><img src="https://agentmods.dev/badge/skills/blake-simpson/belmont/status.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.00011 | $0.02141 |
| Opus 5 | $0.00005 | $0.01071 |
| Sonnet 5 | $0.00002 | $0.00428 |
| Haiku 4.5 | $0.00001 | $0.00214 |
Grade A, and why
status 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 5d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Belmont: Status
Read the current project state and produce a formatted status report.
Fast Path (Preferred)
If available, use the global CLI first:
belmont status --color=always
(--color=always forces ANSI colors on the status markers even though stdout is piped by the calling AI tool — the markers render in colour in the tool's output block, making the list easier to scan.)
If the command fails, fall back to the manual steps below.
Modes
Feature Listing Mode (default)
When no specific feature is requested:
- Read
.belmont/PR_FAQ.md— check if it exists and has content - Read
.belmont/PRD.md— the master PRD (feature catalog) - Scan
.belmont/features/for subdirectories - For each feature directory, read its
PRD.mdfor the feature name andPROGRESS.mdfor task counts - Archived features — a feature directory that contains
ARCHIVE.md(placed there by/belmont:cleanup) has noPROGRESS.md. Omit archived features entirely from the default listing. Only when the user explicitly asks for them, append a compactArchived (N):block (slug — name per line) below the active features. - Produce a feature listing report (see format below)
If no features exist yet, tell the user to run /belmont:product-plan to create their first feature.
If the user ran the CLI fast path above, the --show-archived flag controls this same behaviour (default: hidden entirely; with flag: compact list).
Single Feature Mode
If a specific feature is requested (user says "show status for auth" or similar):
- Set base path to
.belmont/features/<slug>/ - Read
{base}/PROGRESS.md— every task state, milestone and count in the report comes from here. - Read
{base}/PRD.mdonly for the feature's name and one-line description. If the report does not need more than that, read the header rather than the whole file. - For
{base}/TECH_PLAN.md,{base}/NOTES.mdand.belmont/NOTES.md, the report states only whether they exist and are non-empty — check existence, do not read their contents. - Produce the standard status report (see format below)
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.
- 5d ago First seen · 196 lines · 11 tokens per session scan A 6ac2183272df
status is a skill published in the GitHub repository blake-simpson/belmont (4 stars, last pushed 16d ago), licensed Apache-2.0. It adds 11 tokens to every session and 2,141 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.