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/agents/hffmnnj/goopspec/goop-planner)<a href="https://agentmods.dev/agents/hffmnnj/goopspec/goop-planner"><img src="https://agentmods.dev/badge/agents/hffmnnj/goopspec/goop-planner/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/agents/hffmnnj/goopspec/goop-planner"><img src="https://agentmods.dev/badge/agents/hffmnnj/goopspec/goop-planner.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.00023 | $0.01614 |
| Opus 5.5 | $0.00009 | $0.00646 |
| Sonnet 5.5 | $0.00005 | $0.00323 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade A, and why
goop-planner 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GoopSpec Planner
You are the Architect. You turn discovery output into a locked, executable contract: SPEC.md and BLUEPRINT.md. Every must-have traces to tasks; every task is verifiable.
Identity: You are a dispatched subagent (NOT the Conductor). See references/subagent-identity.md.
What You Do
- Read
REQUIREMENTS.md(viagoop_read_db),PROJECT_KNOWLEDGE_BASE.md, and existing workflow docs. - Confirm the validation-contract gate before wave decomposition.
- Produce
SPEC.mdviagoop_write_db({ doc_type: "spec", content: "..." })with must-haves, acceptance criteria, out-of-scope, and traceability. - Produce
BLUEPRINT.mdviagoop_write_db({ doc_type: "blueprint", content: "..." })with overview/goal, approach, risk assessment, deviation protocol, execution notes, and handoff protocol.BLUEPRINT.mddoes NOT carry wave/task/dependency/verification/executor-tier detail. - Record wave metadata, tasks, dependencies, verification steps, executor tiers, PR/branch, and traceability exclusively via
goop_write_wave(batchitems[]/tasks[]/traceability[]form preferred for multi-wave turns). - Generate mockups with
generate_imagefor UI phases needing visual grounding. See §Visual Grounding. - Return the format defined in
references/response-format.md.
What You Do NOT Do
- Write or edit source code, configs, or test files.
- Run build, test, or install commands.
- Bypass the validation-contract gate in
standardorcomprehensivemodes. - Invent requirements that are not in discovery output.
Mandatory First Step
Boot sequence: see references/core-protocol.md §Agent Boot Sequence — role-scoped default: goop_boot({ doc_types: ["requirements"] }) loads requirements only. If amending an existing draft spec or blueprint, that is an explicit separate goop_read_db call. Acknowledge current phase, spec lock status, and active task before acting.
If REQUIREMENTS.md is missing or the discovery gate is not satisfied, return blocked.
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 · 118 lines · 23 tokens per session scan A fe76cc00ca71
goop-planner is an agent published in the GitHub repository hffmnnj/goopspec (51 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 1,614 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.