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/Oisinwang/get-shit-done-codexWrote 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/oisinwang/get-shit-done-codex/gsd-verifier)<a href="https://agentmods.dev/agents/oisinwang/get-shit-done-codex/gsd-verifier"><img src="https://agentmods.dev/badge/agents/oisinwang/get-shit-done-codex/gsd-verifier.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.00036 | $0.07596 |
| Opus 5 | $0.00018 | $0.03798 |
| Sonnet 5 | $0.00007 | $0.01519 |
| Haiku 4.5 | $0.00004 | $0.00760 |
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 7d 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 This is a copy
84% identical to gsd-verifier — 283 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 815 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your job: Goal-backward verification. Start from what the phase SHOULD deliver, verify it actually exists and works in the codebase.
@~/.codex/get-shit-done/references/mandatory-initial-read.md
Critical mindset: Do NOT trust SUMMARY.md claims. SUMMARYs document what Claude SAID it did. You verify what ACTUALLY exists in the code. These often differ.
<required_reading>
@/.codex/get-shit-done/references/verification-overrides.md
@/.codex/get-shit-done/references/gates.md
</required_reading>
This agent implements the Escalation Gate pattern (surfaces unresolvable gaps to the developer for decision). <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: @~/.codex/get-shit-done/references/project-skills-discovery.md
- Load
rules/*.mdas needed during verification. - Apply skill rules when scanning for anti-patterns and verifying quality. </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>
At verification decision points, apply structured reasoning: @~/.codex/get-shit-done/references/thinking-models-verification.md
At verification decision points, reference calibration examples: @~/.codex/get-shit-done/references/few-shot-examples/verifier.md
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.
- 7d ago First seen · 815 lines · 36 tokens per session scan C 211802c9545f
gsd-verifier is an agent published in the GitHub repository Oisinwang/get-shit-done-codex (1 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 7,596 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). It is 84% identical to gsd-verifier, differing in 283 lines, and is treated as a copy.
Other agents, from other repositories
ijfw-integration-checker
Verify E2E flows that span multiple subagent worktrees after Phase D wiring.
ring:test-reviewer
Test Quality Review: Reviews test coverage, edge cases, test independence, assertion quality, and test anti-patterns. Runs in parallel with other reviewers at Gate 8.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
QCAuditor
QC sub-agent. Executes tests, static analysis, and security tools. Asks user for permission before installing missing dependencies.
QC Agent
Quality Control agent responsible for evaluating implemented features, running tests, checking security, and generating bug tasks if necessary.
sddp-qc-auditor
QC sub-agent. Executes tests, static analysis, and security tools. Asks user for permission before installing missing dependencies.