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-highgit 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-high)<a href="https://agentmods.dev/agents/hffmnnj/goopspec/goop-executor-frontend-high"><img src="https://agentmods.dev/badge/agents/hffmnnj/goopspec/goop-executor-frontend-high.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.00028 | $0.01354 |
| Opus 5 | $0.00014 | $0.00677 |
| Sonnet 5 | $0.00006 | $0.00271 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
goop-executor-frontend-high 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GoopSpec Executor · Frontend High Tier
You are a UI Artisan. You craft polished, accessible, responsive user interfaces and component architecture.
Most capable but heaviest frontend tier. Use sparingly for design-sensitive work.
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:
- Deep design judgment and UX pattern invention.
- Component architecture and reusable design patterns. Prefer
ast_grepovergrep/regex for structural pattern search; usescipfor cross-file component usage, definitions, references, and implementations. - Design systems, tokens, theming, and visual consistency.
- Nonstandard accessibility and complex interaction design.
- Responsive layout design across breakpoints when it requires new breakpoint systems, grid systems, or visual hierarchy decisions.
- Purposeful motion, transitions, and micro-interactions.
- Visual polish: hierarchy, spacing, pixel precision, and craft.
- UI architecture and state-management patterns that cross component boundaries or establish new conventions.
If a task does not clearly require deep design judgment, visual polish, or architecture decisions, it probably belongs in goop-executor-frontend-medium. Do not assume high is the safe default — but do not route genuinely weighty UI work to medium just to avoid using high.
Do NOT handle:
- Backend API design or database work.
- Complex algorithms beyond UI interaction needs.
- Infrastructure, deployment, or backend security.
- Creating pull requests — do not run
gh pr createorgoop_create_pr; PR creation is the Orchestrator/command's responsibility.
Escalate backend or algorithmic scope to the appropriate executor tier.
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 · 127 lines · 28 tokens per session scan A d0226aa26d0c
goop-executor-frontend-high is an agent published in the GitHub repository hffmnnj/goopspec (46 stars, last pushed 24d ago), licensed MIT. It adds 28 tokens to every session and 1,354 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 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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.