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/hffmnnj/goopspec/goop-plangit clone --depth 1 https://github.com/hffmnnj/goopspecWrote 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/hffmnnj/goopspec/goop-plan)<a href="https://agentmods.dev/commands/hffmnnj/goopspec/goop-plan"><img src="https://agentmods.dev/badge/commands/hffmnnj/goopspec/goop-plan.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.00908 |
| Opus 5 | $0.00005 | $0.00454 |
| Sonnet 5 | $0.00002 | $0.00182 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
goop-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 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/goop-plan
Turn the requirements document into a locked contract (SPEC.md) and an executable wave plan (BLUEPRINT.md).
Gate check
Call goop_state({ action: "get" }). If interviewComplete is not true or the requirements document does not exist — check via goop_read_db({ doc_type: "requirements" }) returning content (not a 'not found' message) — return BLOCKED with:
Run
/goop-discussfirst.
Research-first gate
Research-first gate: see agents/goop-orchestrator.md §Research-First Gate (Plan Phase) for the full procedure — dispatch rules, skip heuristic, fallback, mid-wave research, and sequencing. The orchestrator owns this gate; this command invokes it.
Load references
goop_reference({ name: "core-protocol" })
goop_reference({ name: "task-decomposition" })
goop_reference({ name: "phase-gates" })
goop_reference({ name: "pr-creation" })
Steps
- Read requirements via
goop_read_db({ doc_types: ["requirements"] }), search memory, and createPROJECT_KNOWLEDGE_BASE.mdif missing. - Complete the Research-first gate above (or record the skip decision in ADL). Then spawn
goop-plannerwith the discovery context, current depth, workflow isolation context, and the assembled## Research Summaryblock. - Review the draft
SPEC.mdandBLUEPRINT.md.
Validation-contract gate
Before wave decomposition is finalized, validate:
- Every must-have maps to one or more tasks.
- Every task maps to a must-have or an explicit enabler.
- Out-of-scope, assumptions, and risks are captured.
- The wave/task plan has 2–4 tasks per wave and clear verification steps (verified via
goop_read_wave). - If atomic PRs enabled (REQUIREMENTS.md
## Atomic PR StrategyisYes): every wave written viagoop_write_wavemust havepr_branchandpr_urlpopulated.
If validation fails, send the planner back to fix gaps.
Lock the spec
Present a contract gate via the question tool (skipped when autopilot is active — see below):
- Confirm and lock (Recommended) →
goop_state({ action: "lock-spec" }), then suggest/goop-execute. - Amend → Edit the draft and re-run the gate.
- Cancel → Keep the spec unlocked.
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 · 84 lines · 11 tokens per session scan A 49a799c09d5e
goop-plan is a command published in the GitHub repository hffmnnj/goopspec (46 stars, last pushed 24d ago), licensed MIT. It adds 11 tokens to every session and 908 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-30.
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.