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.
npx skills add shoootyou/get-shit-done-multi --skill gsd-verify-workgit clone --depth 1 https://github.com/shoootyou/get-shit-done-multiWrote 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/skills/shoootyou/get-shit-done-multi/gsd-verify-work)<a href="https://agentmods.dev/skills/shoootyou/get-shit-done-multi/gsd-verify-work"><img src="https://agentmods.dev/badge/skills/shoootyou/get-shit-done-multi/gsd-verify-work/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/skills/shoootyou/get-shit-done-multi/gsd-verify-work"><img src="https://agentmods.dev/badge/skills/shoootyou/get-shit-done-multi/gsd-verify-work.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.00013 | $0.00304 |
| Opus 5 | $0.00006 | $0.00152 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
gsd-verify-work 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.
What it actually says
Purpose: Confirm what Claude built actually works from user's perspective. One test at a time, plain text responses, no interrogation. When issues are found, automatically diagnose, plan fixes, and prepare for execution.
Output: {phase_num}-UAT.md tracking all test results. If issues found: diagnosed gaps, verified fix plans ready for {{COMMAND_PREFIX}}execute-phase
<execution_context> @{{PLATFORM_ROOT}}/get-shit-done/workflows/verify-work.md @{{PLATFORM_ROOT}}/get-shit-done/templates/UAT.md </execution_context>
Context files are resolved inside the workflow (init verify-work) and delegated via <files_to_read> blocks.
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 · 32 lines · 13 tokens per session scan A a280f88672f0
gsd-verify-work is a skill published in the GitHub repository shoootyou/get-shit-done-multi (22 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 304 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-31.
Other skills, from other repositories
gsd-verify-work
Validate built features through conversational UAT.
gsd-add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
gsd-audit-uat
Cross-phase audit of all outstanding UAT and verification items.
gsd-eval-review
Audit an executed AI phase's evaluation coverage and produce an EVAL-REVIEW.md remediation plan.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
tdd
Test-driven development with red-green-refactor loops around vertical slices (tracer bullets), not horizontal layers. Use when asked to "use TDD", "write test-first", "red-green-refactor", "build this with tests", or when a feature has a clear observable contract. The discipline complement to the test/add-tests skills…