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-statusgit 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-status)<a href="https://agentmods.dev/commands/hffmnnj/goopspec/goop-status"><img src="https://agentmods.dev/badge/commands/hffmnnj/goopspec/goop-status.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.00014 | $0.00263 |
| Opus 5 | $0.00007 | $0.00131 |
| Sonnet 5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
goop-status 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.
What it actually says
/goop-status
Display the current workflow state and suggest the next command.
Immediate action
Call the status tool directly:
goop_status({ verbose: true })
What to show
- Active workflow and phase.
- Gate status:
interviewComplete,specLocked,allWavesComplete. - Current wave and total waves.
- Pending blockers or deviations.
- Suggested next command based on state.
Suggested next commands
| State | Next command |
|---|---|
No .goopspec |
/goop-setup |
| Interview incomplete | /goop-discuss |
| Interview done, no locked spec | /goop-plan |
| Spec locked | /goop-execute |
| Executing | /goop-execute |
| All waves complete | /goop-accept |
| Accepted | /goop-discuss |
Anti-patterns
- Guess state instead of reading it.
- Suggest a command that the current gate does not allow.
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 · 46 lines · 14 tokens per session scan A 7127052447ef
goop-status is a command published in the GitHub repository hffmnnj/goopspec (46 stars, last pushed 23d ago), licensed MIT. It adds 14 tokens to every session and 263 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
clarify
Walk through inbox items applying the GTD decision tree. Usage: /gtd:clarify [--id gtd-xxx].