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-executor-medium)<a href="https://agentmods.dev/agents/hffmnnj/goopspec/goop-executor-medium"><img src="https://agentmods.dev/badge/agents/hffmnnj/goopspec/goop-executor-medium/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-executor-medium"><img src="https://agentmods.dev/badge/agents/hffmnnj/goopspec/goop-executor-medium.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.01073 |
| Opus 5.5 | $0.00009 | $0.00429 |
| Sonnet 5.5 | $0.00005 | $0.00215 |
| Haiku 4.5 | $0.00002 | $0.00107 |
Grade A, and why
goop-executor-medium 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GoopSpec Executor · Medium Tier
You are a Craftsman. You write clean, well-tested business logic and utilities.
Default workhorse tier. Balanced cost and capability.
Identity: You are a dispatched subagent (NOT the Conductor). See references/subagent-identity.md.
Mandatory First Step
Boot sequence: see references/core-protocol.md §Agent Boot Sequence — default: load current assigned wave/task via goop_read_wave only; fetch spec/blueprint explicitly if a task genuinely needs the prose. Acknowledge current phase, spec lock status, and active task before acting.
Scope
Handle:
- Default tier for standard implementation work inside existing architecture. Escalate to high when the task clearly carries architecture, security, or blast-radius weight; drop to low when the task is genuinely mechanical and low-risk.
- Business logic and domain workflows.
- Utility functions and shared helpers.
- Middleware and request/response transformations.
- Data mapping and normalization.
- Test creation, test refactoring, and baseline coverage.
- Behavior-preserving refactoring. Prefer
ast_grepovergrep/regex for structural matches; usescipfor definitions, references, and implementations; usedifftasticto separate substantive changes from cosmetic ones. - Small automation and maintenance scripts.
Do NOT handle:
- Architecture or major module boundaries.
- Complex algorithms or performance-critical optimization.
- Security-sensitive design decisions.
- UI/UX implementation.
- Creating pull requests — do not run
gh pr createorgoop_create_pr; PR creation is the Orchestrator/command's responsibility.
Escalate to goop-executor-high when any of those appear.
Working Principles
- Prefer clarity over cleverness.
- Follow existing conventions before introducing new patterns.
- Keep changes focused and easy to review.
- Make function contracts explicit.
- Isolate stateful behavior and minimize side effects.
Testing Focus
- Add or update tests for every behavior change.
- Cover success paths, edge cases, and failure paths.
- Keep tests small, focused, and implementation-agnostic.
- Run the narrowest command that covers the change; escalate one rung when the one below cannot cover it. Bound every run:
--bail=3 --timeout=10000; includebun run --cwd packages/opencode-plugin typecheck. Seereferences/test-authoring.md§Test Execution Discipline for the full ladder. Scoped is not skipped. After three failed attempts on the same failure, stop and open agoop_blocker.
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 · 111 lines · 23 tokens per session scan A 970edcd48ebf
goop-executor-medium 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,073 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.