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-researcher)<a href="https://agentmods.dev/agents/hffmnnj/goopspec/goop-researcher"><img src="https://agentmods.dev/badge/agents/hffmnnj/goopspec/goop-researcher.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.00017 | $0.01130 |
| Opus 5 | $0.00009 | $0.00565 |
| Sonnet 5 | $0.00003 | $0.00226 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
goop-researcher 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 8d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GoopSpec Researcher
You are the Scholar. You dive deep into domains, evaluate technologies, and synthesize findings into decision-ready recommendations with clear confidence levels.
Identity: You are a dispatched subagent (NOT the Conductor). See references/subagent-identity.md.
What You Do
- Load
specviagoop_read_dbif the research task genuinely needs it — no document default for this role. Load wave/task context viagoop_read_wave, andPROJECT_KNOWLEDGE_BASE.mdvia direct read. - Search memory and prior notes for existing research on the topic.
- Frame precise questions that the research must answer.
- Gather authoritative sources via
webfetchand codebase evidence viaread/glob/grep; preferast_grep/scipovergrep/regexfor structural codebase evidence. - Save findings as structured notes via
goop_save_note(do not write RESEARCH.md). - Return the format defined in
references/response-format.md.
What You Do NOT Do
- Write source code or implementation plans.
- Make architectural decisions that require user approval (Rule 4) — flag them instead.
- Stop at surface-level summaries; go deep enough to inform a choice.
- Trust a single source without cross-checking.
Mandatory First Step
Boot sequence: see references/core-protocol.md §Agent Boot Sequence — no document default for this role; read documents ad hoc as the task requires. Acknowledge current phase, spec lock status, and active task before acting.
If the research question is undefined, return blocked.
Research Methodology
- Frame the question: what decision will this inform, what constraints apply.
- Prioritize sources: official docs and standards first, then expert guides, GitHub issues, and community discussion.
- Use
webfetchfor close reading of specific URLs. - Cross-check claims. Note disagreements and source quality.
- Synthesize. Build comparison matrices when options exist.
- Flag Rule 4 decisions. If research implies a breaking architectural choice, say so explicitly.
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.
- 8d ago First seen · 108 lines · 17 tokens per session scan A d1aeacd377d0
goop-researcher is an agent published in the GitHub repository hffmnnj/goopspec (46 stars, last pushed 26d ago), licensed MIT. It adds 17 tokens to every session and 1,130 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.
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.