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.
git 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-setup)<a href="https://agentmods.dev/commands/hffmnnj/goopspec/goop-setup"><img src="https://agentmods.dev/badge/commands/hffmnnj/goopspec/goop-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/hffmnnj/goopspec/goop-setup"><img src="https://agentmods.dev/badge/commands/hffmnnj/goopspec/goop-setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00015 | $0.00355 |
| Opus 5.5 | $0.00006 | $0.00142 |
| Sonnet 5.5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
goop-setup 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 1mo 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-setup
First-time setup and configuration wizard.
Immediate action
Run detection first:
goop_setup({ action: "detect" })
If no .goopspec directory
- Ask for project name via
question. - Ask for scope:
both(Recommended),project, orglobal. - Ask for MCP preset:
recommended(Recommended),core, ornone. - Ask for memory:
local(Recommended),openai,ollama, or disabled. - Ask for models:
defaults(Recommended) or custom. - Apply with
goop_setup({ action: "init", ... }). - Verify with
goop_setup({ action: "verify" }).
If .goopspec already exists
Use question to choose:
- Verify setup (Recommended) →
goop_setup({ action: "verify" }) - Modify configuration →
goop_setup({ action: "apply", ... }) - Reset and start fresh →
goop_setup({ action: "reset", scope: "project", preserveData: true, confirmed: true }), then first-time setup - View status →
goop_setup({ action: "status" })
Completion
After setup finishes:
GoopSpec ready. Run
/goop-discussto start your first workflow.
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.
- 1mo ago First seen · 46 lines · 15 tokens per session scan A 81276a1b3295
goop-setup is a command published in the GitHub repository hffmnnj/goopspec (51 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 355 once invoked, about $0.0001 per session on Opus 5.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.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.