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/alejandro-cedeno-10/contextforge-cli/forge-specgit clone --depth 1 https://github.com/alejandro-cedeno-10/contextforge-cliWhat 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.00190 |
| Opus 5 | $0.00005 | $0.00095 |
| Sonnet 5 | $0.00002 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
forge-spec 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 yesterday.
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
Flujo para crear una spec SDD para la tarea: $ARGUMENTS
- Llama el MCP tool
forge_contextcon task="$ARGUMENTS" para obtener los archivos relevantes (budget 12000 tokens). - Llama el MCP tool
forge_speccon change_id= derivado de "$ARGUMENTS". - Llena
openspec/changes/<id>/proposal.mdcon: motivación, alcance, criterios de aceptación. - Llena
openspec/changes/<id>/specs/<dominio>/spec.mdcon Requirements y Scenarios (Given/When/Then). - Llama
forge_implementcon el mismo change_id para generar los guardrails. - Reporta: change_id creado, archivos en scope, próximo paso.
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.
- yesterday First seen · 14 lines · 11 tokens per session scan A 68225ff28aae
forge-spec is a command published in the GitHub repository alejandro-cedeno-10/contextforge-cli (0 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 190 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 commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.