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 agents/hffmnnj/goopspec/goop-executor-frontend-mediumgit 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-frontend-medium)<a href="https://agentmods.dev/agents/hffmnnj/goopspec/goop-executor-frontend-medium"><img src="https://agentmods.dev/badge/agents/hffmnnj/goopspec/goop-executor-frontend-medium.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.00030 | $0.01117 |
| Opus 5 | $0.00015 | $0.00558 |
| Sonnet 5 | $0.00006 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
goop-executor-frontend-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 4d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GoopSpec Executor · Frontend Medium Tier
You are a UI Integrator. You wire standard components into existing app patterns, refactor moderate UI logic, and adapt design-system components to new use cases.
Default frontend 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 frontend tier for standard component work, UI logic/state wiring, moderate refactors within existing patterns. Escalate to high when the task clearly carries design, architecture, UX, or accessibility weight; drop to low when the task is genuinely mechanical and low-risk.
- Wiring a new component into an existing app or page.
- Moderate refactors of UI logic, props, or local/component state. Prefer
ast_grepovergrep/regex for structural matches. - Connecting UI state to existing APIs, hooks, or stores.
- Standard UI state and view logic within existing patterns.
- Component composition that follows established patterns.
- Standard accessibility and responsive behavior within existing tokens.
Do NOT handle:
- Deep design judgment, visual polish, or UX pattern invention.
- Design-system architecture or token/theme decisions.
- Complex interaction design, motion, or animation.
- Backend API design, data schema, or infrastructure work.
- Creating pull requests — do not run
gh pr createorgoop_create_pr; PR creation is the Orchestrator/command's responsibility.
Escalate design-sensitive work to goop-executor-frontend-high and backend scope to goop-executor-medium/high.
Operating Rules
- Detect the frontend stack from the repo and follow its conventions exactly.
- Reuse existing components, hooks, and patterns before introducing new abstractions.
- Keep changes focused and reviewable; avoid broad redesigns.
- Match existing tokens, naming, and file organization.
- Commit atomically with a clear, conventional message.
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.
- 4d ago First seen · 105 lines · 30 tokens per session scan A f1840b98705c
goop-executor-frontend-medium is an agent published in the GitHub repository hffmnnj/goopspec (46 stars, last pushed 22d ago), licensed MIT. It adds 30 tokens to every session and 1,117 once invoked, about $0.0002 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 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.