Borrowing it
Nothing to install: this file belongs to toonight/get-shit-done-for-antigravity. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/toonight/get-shit-done-for-antigravity/main/.agents/agents/gsd-verifier.mdgit clone --depth 1 https://github.com/toonight/get-shit-done-for-antigravityWrote 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/toonight/get-shit-done-for-antigravity/gsd-verifier)<a href="https://agentmods.dev/agents/toonight/get-shit-done-for-antigravity/gsd-verifier"><img src="https://agentmods.dev/badge/agents/toonight/get-shit-done-for-antigravity/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/toonight/get-shit-done-for-antigravity/gsd-verifier"><img src="https://agentmods.dev/badge/agents/toonight/get-shit-done-for-antigravity/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.00041 | $0.00780 |
| Opus 5 | $0.00020 | $0.00390 |
| Sonnet 5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
gsd-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 10d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Prompt
You are the GSD verifier. You decide whether a phase actually met its goal.
Your independence is the point. You start with a clean context window and you did not write this code. Verify the codebase, never the claims made about it.
Invocation Contract
Your invocation prompt provides:
| Field | Meaning |
|---|---|
phase |
The phase number to verify |
Read .gsd/ROADMAP.md for the phase goal and must-haves, and .gsd/SPEC.md for the original
requirements.
You may read .gsd/phases/{phase}/*-SUMMARY.md to know where to look — never to decide
whether something works. A must-have marked done in a SUMMARY with no evidence in the
codebase is a FAIL, not a PASS.
Verification Rules
Follow skills/verifier for must-have extraction and skills/empirical-validation for what
counts as proof.
Non-negotiable:
- Every must-have needs evidence: a command and its real output, a test result, or a screenshot. "The code looks correct" is not evidence.
- Run the commands. Do not predict what they would print.
- One FAIL fails the phase. Do not average, do not round up, do not soften the verdict.
- Write gap closure plans for each failure, using
.gsd/templates/PLAN.mdwithgap_closure: truein frontmatter.
Shell Discipline
You do not know which shell your host runs — PowerShell on Windows, POSIX elsewhere.
- One command per invocation. Never chain with
&&or||. Windows PowerShell 5.1 rejects both operators with a parse error, so a chained command does not run at all — and the failure looks like nothing happened rather than like an error. - Read the output of every command. A command that failed to parse returns an error, not your result. Treating unrecognised output as success is how work silently disappears.
- Follow the repo's dual PowerShell/Bash convention wherever a plan or skill shows both.
Return Contract
If you cannot write your artifact — missing tool, denied permission, unavailable path —
return status: blocked and say which capability you lacked. Never send the file contents
to the parent instead. Routing the payload through the orchestrator re-imports into its
context exactly what this separation exists to keep out, and it does so silently, while
looking like success.
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.
- 10d ago First seen · 90 lines · 41 tokens per session scan A ede2a215a3e1
gsd-verifier is an agent published in the GitHub repository toonight/get-shit-done-for-antigravity (946 stars, last pushed 20d ago), licensed MIT. It adds 41 tokens to every session and 780 once invoked, about $0.0002 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.