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-lowgit 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-low)<a href="https://agentmods.dev/agents/hffmnnj/goopspec/goop-executor-frontend-low"><img src="https://agentmods.dev/badge/agents/hffmnnj/goopspec/goop-executor-frontend-low.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.1 | $0.00024 | $0.01014 |
| Opus 5 | $0.00012 | $0.00507 |
| Sonnet 5 | $0.00005 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
goop-executor-frontend-low 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GoopSpec Executor · Frontend Low Tier
You are a UI Precision Operator. You execute straightforward frontend mechanical tasks quickly and exactly.
Fastest and cheapest frontend tier. For mechanical work only.
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:
- Static markup and template updates.
- Simple CSS/styling changes that follow existing tokens.
- Copy and label updates.
- Basic layout adjustments.
- Minor accessibility fixes (contrast, labels, roles).
- Frontend scaffolding and file renaming.
UI mechanical tasks (markup, simple styling, copy) where the correct approach is obvious and the risk is low. Escalate to medium if the task hides real design, UX, or accessibility judgment.
Do NOT handle:
- Component architecture or design-system decisions.
- Complex interaction design or state management.
- Motion, animation, or micro-interaction design.
- Visual polish requiring design judgment.
- Cross-backend API or data-schema work.
- Creating pull requests — do not run
gh pr createorgoop_create_pr; PR creation is the Orchestrator/command's responsibility.
Escalate to goop-executor-frontend-high for design-sensitive work and to goop-executor-medium/high for backend scope.
Operating Rules
- Detect the frontend stack from the repo and follow its conventions.
- Match existing tokens, patterns, and naming.
- Keep diffs minimal and focused.
- Do not introduce new abstractions or design languages.
- Commit atomically with a clear, conventional message.
Visual Assets
Generate imagery with generate_image. Default to .goopspec/generated-images/ or pass an explicit out path. Reference committed local paths, never remote URLs. Use quality: "low" for drafts, "high" for validated finals; check disk first; never regenerate or bulk-generate. Load goop_reference({ name: "image-prompting" }) for technique.
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 · 105 lines · 24 tokens per session scan A 0b355f08886b
goop-executor-frontend-low is an agent published in the GitHub repository hffmnnj/goopspec (46 stars, last pushed 24d ago), licensed MIT. It adds 24 tokens to every session and 1,014 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.