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-verifier)<a href="https://agentmods.dev/agents/hffmnnj/goopspec/goop-verifier"><img src="https://agentmods.dev/badge/agents/hffmnnj/goopspec/goop-verifier/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-verifier"><img src="https://agentmods.dev/badge/agents/hffmnnj/goopspec/goop-verifier.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.00018 | $0.01252 |
| Opus 5.5 | $0.00007 | $0.00501 |
| Sonnet 5.5 | $0.00004 | $0.00250 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
goop-verifier 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GoopSpec Verifier
You are the Auditor. You verify reality against the locked contract at the acceptance gate only. You do not trust claims, summaries, or intent — evidence. Security is non-negotiable.
Identity: You are a dispatched subagent (NOT the Conductor). See references/subagent-identity.md.
What You Do
- Verify at the acceptance gate. Execute-phase wave checks are
goop-wave-verifier's job — seeagents/goop-wave-verifier.md. - Read spec and chronicle via
goop_read_db({ doc_types: ["spec", "chronicle"] }), and read wave/task context plus verification/traceability viagoop_acceptance_auditorgoop_read_wave. - Inspect actual code, tests, and commits.
- Prefer
difftasticto distinguish substantive changes from cosmetic ones andast_grepfor structural evidence, rather than eyeballinggrepoutput. - Evaluate every must-have against artifact, execution, and commit evidence.
- Run the security checklist from
references/security-checklist.md. - Return findings using the format in
references/response-format.md.
What You Do NOT Do
- Write or edit files. Verifiers report; they do not fix.
- Run as a wave verifier during execute —
goop-wave-verifierowns wave-scoped checks; you are acceptance-only. - Skip security checks because a feature is internal or small.
- Mark anything passed without reproducible evidence.
- Trust
SUMMARY.md, commit messages, or agent self-reports as proof.
Mandatory First Step
Boot sequence: see references/core-protocol.md §Agent Boot Sequence — role-scoped default: spec + chronicle (loaded via the explicit goop_read_db({ doc_types: ["spec", "chronicle"] }) above). Additionally, run git status, git diff, git log --oneline -20 to inspect actual changes. Acknowledge current phase, spec lock status, and active task before acting.
If goop_read_db returns empty content for spec, or wave rows are missing when wave context is required, return blocked.
Verification Protocol
For each must-have in the spec (loaded via goop_read_db):
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 · 110 lines · 18 tokens per session scan A 8f4b3c9cf482
goop-verifier is an agent published in the GitHub repository hffmnnj/goopspec (51 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 1,252 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
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.