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-helpgit 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-help)<a href="https://agentmods.dev/commands/hffmnnj/goopspec/goop-help"><img src="https://agentmods.dev/badge/commands/hffmnnj/goopspec/goop-help.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.00015 | $0.00606 |
| Opus 5 | $0.00008 | $0.00303 |
| Sonnet 5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
goop-help 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/goop-help
Show available commands and workflow overview.
Available commands
| Command | Purpose |
|---|---|
/goop-discuss [workflow-id] |
Start the discovery interview |
/goop-plan |
Create locked spec and blueprint |
/goop-execute |
Execute blueprint waves |
/goop-accept |
Verify, accept, and archive |
/goop-quick [task] |
Fast-track a small task |
/goop-amend [change] |
Propose changes to a locked spec |
/goop-status |
Show current workflow status |
/goop-setup |
Setup and configuration wizard |
/goop-help |
Show this help |
Five-phase workflow
See references/core-protocol.md §Five-Phase Workflow for the full phase table and gate semantics.
Agents
One orchestrator, fourteen specialists. The orchestrator delegates and never implements.
goop-orchestrator— workflow conductor.goop-planner— spec and blueprint authoring.goop-executor-low— mechanical/pattern-following edits; escalate if hidden complexity.goop-executor-medium— standard implementation work; default when a task isn't clearly mechanical or complex/critical.goop-executor-high— architecture-sensitive or security-critical work; use when genuinely warranted.goop-executor-frontend-low— UI mechanical tasks; escalate if hidden complexity.goop-executor-frontend-medium— standard UI component work; default when UI work isn't clearly mechanical or design/architectural.goop-executor-frontend-high— deep design or UI-architecture work; use when genuinely warranted.goop-researcher— domain and technology research.goop-explorer— codebase mapping.goop-wave-verifier— per-wave verification during execute; scoped to one wave, inspect/report-only, never implements fixes.goop-verifier— acceptance-only; spec compliance and security audit at the accept gate.goop-tester— tests and QA.goop-debugger— scientific debugging.goop-writer— documentation.
Auto-routed intents
Saying "research X" or "debug Y" does not require a dedicated command. The orchestrator routes these to goop-researcher or goop-debugger automatically.
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 · 59 lines · 15 tokens per session scan A 2c7ee21e0b8a
goop-help is a command published in the GitHub repository hffmnnj/goopspec (46 stars, last pushed 22d ago), licensed MIT. It adds 15 tokens to every session and 606 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
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.