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/flagler-county-bocc/mcp-forge/forge-stepgit clone --depth 1 https://github.com/Flagler-County-BoCC/mcp-forgeWrote 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/flagler-county-bocc/mcp-forge/forge-step)<a href="https://agentmods.dev/commands/flagler-county-bocc/mcp-forge/forge-step"><img src="https://agentmods.dev/badge/commands/flagler-county-bocc/mcp-forge/forge-step.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.00236 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
forge-step 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 3d 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
Apply a specific mcp-forge rewrite step to this project.
Usage: /forge-step 1 — apply step 1 (all project types) /forge-step 8 mcp-server — apply step 8 for a specific project type
Arguments: $ARGUMENTS
Steps:
- Parse $ARGUMENTS — first token is the step number, optional second token is the project type
- If no step number is provided, tell the user the correct usage and stop
- Call the
get_steptool from mcp-forge with the parsed step number and project type - If the tool returns an error (e.g. step 8 needs a project type), surface the error clearly and stop
- Apply the returned prompt to the current codebase — write or rewrite files as instructed
- Show a clear summary of every file created or modified
- Suggest the next step:
/forge-step <n+1>(or/forge-step 8 <projectType>if step 7 just completed)
Note: always run /forge-audit first if no AUDIT_MANIFEST exists yet.
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.
- 3d ago First seen · 19 lines · 0 tokens per session scan A ccbc1aedc3d4
forge-step is a command published in the GitHub repository Flagler-County-BoCC/mcp-forge (1 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 236 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.