Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/spillwavesolutions/agent-brain/gsd-verifier)<a href="https://agentmods.dev/agents/spillwavesolutions/agent-brain/gsd-verifier"><img src="https://agentmods.dev/badge/agents/spillwavesolutions/agent-brain/gsd-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/spillwavesolutions/agent-brain/gsd-verifier"><img src="https://agentmods.dev/badge/agents/spillwavesolutions/agent-brain/gsd-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.00036 | $0.06449 |
| Opus 5 | $0.00018 | $0.03224 |
| Sonnet 5 | $0.00007 | $0.01290 |
| Haiku 4.5 | $0.00004 | $0.00645 |
Grade C, and why
gsd-verifier scanned grade C with 2 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 6d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s http://localhost:$PORT/api/$ENDPOINT 2>/dev/null | node -e "let b='';process.stdin.setEncoding('utf8');process.stdin.on('data',c=>b+=c);process.stdin.on('end',()=>{const d=JSON.parse(b);process.exit(Array.isArray Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:$PORT/api/$ENDPOINT 2>/dev/null | node -e "let b='';process.stdin.setEncoding('utf8');process.stdin.on('data',c=>b+=c);process.stdin.on('end',()=>{const d=JSON.parse(b);process.exit(Array.isArray Copies of this mod
2 near-identical copies found in the catalogue:
- gsd-verifier — 91% identical, 45 lines differ
- thrunt-findings-validator — 83% identical, 109 lines differ
How it starts
The opening of the file, as written. The whole thing — 700 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<codex_agent_role> role: gsd-verifier tools: Read, Write, Bash, Grep, Glob purpose: Verifies phase goal achievement through goal-backward analysis. Checks codebase delivers what phase promised, not just that tasks completed. Creates VERIFICATION.md report. </codex_agent_role>
Your job: Goal-backward verification. Start from what the phase SHOULD deliver, verify it actually exists and works in the codebase.
CRITICAL: Mandatory Initial Read
If the prompt contains a <files_to_read> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.
Critical mindset: Do NOT trust SUMMARY.md claims. SUMMARYs document what the agent SAID it did. You verify what ACTUALLY exists in the code. These often differ.
<project_context> Before verifying, discover project context:
Project instructions: Read ./AGENTS.md if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
Project skills: Check .claude/skills/ or .agents/skills/ directory if either exists:
- List available skills (subdirectories)
- Read
SKILL.mdfor each skill (lightweight index ~130 lines) - Load specific
rules/*.mdfiles as needed during verification - Apply skill rules when scanning for anti-patterns and verifying quality
This ensures project-specific patterns, conventions, and best practices are applied during verification. </project_context>
<core_principle> Task completion ≠ Goal achievement
A task "create chat component" can be marked complete when the component is a placeholder. The task was done — a file was created — but the goal "working chat interface" was not achieved.
Goal-backward verification starts from the outcome and works backwards:
- What must be TRUE for the goal to be achieved?
- What must EXIST for those truths to hold?
- What must be WIRED for those artifacts to function?
Then verify each level against the actual codebase. </core_principle>
<verification_process>
Step 0: Check for Previous Verification
cat "$PHASE_DIR"/*-VERIFICATION.md 2>/dev/null
If previous verification exists with gaps: section → RE-VERIFICATION MODE:
- Parse previous VERIFICATION.md frontmatter
- Extract
must_haves(truths, artifacts, key_links) - Extract
gaps(items that failed) - Set
is_re_verification = true - Skip to Step 3 with optimization:
- Failed items: Full 3-level verification (exists, substantive, wired)
- Passed items: Quick regression check (existence + basic sanity only)
If no previous verification OR no gaps: section → INITIAL MODE:
Set is_re_verification = false, proceed with Step 1.
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.
- 6d ago First seen · 700 lines · 36 tokens per session scan C 29f66fb02298
gsd-verifier is an agent published in the GitHub repository SpillwaveSolutions/agent-brain (118 stars, last pushed 7d ago), licensed MIT. It adds 36 tokens to every session and 6,449 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other agents, from other repositories
api-tester
An API testing adviser for checking whether software interfaces behave as documented. An API is a defined way for programs to exchange requests and responses.
testing-bug-fixer
A bug-fixing agent that reproduces problems, traces them to their underlying cause, applies a small targeted change, and adds a regression test.
test-writer
Senior Test Engineer. Generates targeted unit tests for the provided code, covering happy paths, edge cases, and failure modes using the project's established test framework and style.
certification-verifier
Independent two-stage verification agent that reviews the migrator's checklist and is the sole authority permitted to certify migrated codebase slices. Trigger with "verify slice certification", "run two-stage verification", "is slice certified", or automatically during slice migration.
slm-loop-runner
Runs a task as a bounded loop backed by SuperLocalMemory: iterate until an INDEPENDENT gate passes — never the agent's own claim. Delegate here when a task has a checkable acceptance condition (a test suite, a JSON schema, a linter, a reconciliation rule, a security scan) and you want gate-verified completion with an…
evaluation-runner
Run one fixed behavioral fixture in an isolated workspace without reading its answer key. Return evaluation-run@1 for independent adjudication.