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/marcmallet/specforge/plangit clone --depth 1 https://github.com/marcmallet/specforgeWhat 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.00009 | $0.00428 |
| Opus 5 | $0.00005 | $0.00214 |
| Sonnet 5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
plan 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
You are helping plan implementation of a feature spec.
Specs directory
Read the project config at: @.claude/specforge/config.json
If the file exists, use the value of the specsDir field as the base directory.
If the file does not exist, fall back to .claude/specforge/ inside the current project.
The full path for this ticket is: /$ARGUMENTS/
Read the feature spec at: /$ARGUMENTS/spec.md
Plan
Then do the following:
- Summarize the feature in 2-3 sentences
- Identify all files that will need to be created or modified in the current project
- Break the work into ordered tasks as a markdown checklist, each small enough to implement and test independently
- Tag every task with one of:
[backend]— server side only, no frontend files touched[frontend]— client side only, no backend files touched[both]— spans both backend and frontend (e.g. a template that needs data bindings AND markup)
- For any task tagged
[both], define the shared contract explicitly:- File(s) involved
- Field names, endpoint paths, data shapes both sides must agree on
- Summarise all shared contracts in a ## Shared Contracts section at the bottom of the plan
- Flag any ambiguities, missing information, or decisions that need to be made before starting
- Estimate complexity: Low / Medium / High and explain why
- Save the final plan to /$ARGUMENTS/plan.md
Do not write any code yet. This is planning only.
After saving the plan, suggest the next step: "Ready to implement? Run /specforge:implement $ARGUMENTS"
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 · 41 lines · 9 tokens per session scan A 044030a943ad
plan is a command published in the GitHub repository marcmallet/specforge (9 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 428 once invoked, about $0.0000 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.