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 AbdurRafay2004/handoff --skill verify-donegit clone --depth 1 https://github.com/AbdurRafay2004/handoffWrote 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/abdurrafay2004/handoff/verify-done)<a href="https://agentmods.dev/skills/abdurrafay2004/handoff/verify-done"><img src="https://agentmods.dev/badge/skills/abdurrafay2004/handoff/verify-done.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.00047 | $0.01575 |
| Opus 5 | $0.00023 | $0.00788 |
| Sonnet 5 | $0.00009 | $0.00315 |
| Haiku 4.5 | $0.00005 | $0.00158 |
Grade A, and why
verify-done 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 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.
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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Done
Part of the Verify phase — see the workflow skill for tiers and sequencing.
Claiming work is complete without verification is dishonesty, not efficiency.
The Iron Law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.
If you haven't run the verification command in this message, you cannot claim it passes.
Why this matters more here
The user reviews outcomes, not code. Evidence — command output, test summaries, screenshots, preview URLs — is the only thing they can judge. An unverified "done" that turns out broken doesn't just cost rework; it breaks the trust the whole PM ↔ engineer division of labor depends on. One false "it works" costs more than ten honest "it's not working yet"s.
The gate function
BEFORE claiming any status or expressing satisfaction:
1. IDENTIFY: what command proves this claim?
2. RUN: the FULL command (fresh, complete)
3. READ: full output, exit code, failure count
4. VERIFY: does the output confirm the claim?
- NO → state the actual status, with the evidence
- YES → state the claim WITH the evidence
5. ONLY THEN: make the claim
Skip any step = lying, not verifying.
What each claim requires
| Claim | Requires | Not sufficient |
|---|---|---|
| Tests pass | Test command output: 0 failures | Previous run, "should pass" |
| Typecheck clean | tsc --noEmit: exit 0 |
Editor showed no squiggles |
| Linter clean | Linter output: 0 errors | Partial check |
| Build succeeds | Build command: exit 0 | Linter passing, logs look fine |
| Bug fixed | Original symptom re-tested: passes | Code changed, assumed fixed |
| Regression test works | Red-green verified (fails without fix, passes with) | Test passes once |
| Subagent completed | Diff inspected, changes verified | Agent reports "success" |
| Requirement match | Diff vs brief, line by line | Tests passing |
The Spec check
"It works" and "it's what was asked" are different claims. Verify both, on separate axes:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 150 lines · 47 tokens per session scan A f549f7cf1704
verify-done is a skill published in the GitHub repository AbdurRafay2004/handoff (4 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,575 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-31.
Other skills, from other repositories
are-you-done
A completion checker for coding work that asks for evidence before allowing an assistant to say a task is finished.
did-you-forget-me
A requirement-checking skill that compares the current work with what the user explicitly asked for. It is written in Korean and includes a fixed Korean report format.
dont-leave-me
A stop-before-finishing checklist for an agent that checks whether requested work, changed files, verification, and cleanup have actually been handled.
show-me-proof
A skill for collecting concrete proof that a coding task was completed, such as changed files, test commands, logs, and remaining risks.
remember
Capture a durable learning into the personal Trove. Use when the user says remember this, note this, save to trove, add to my trove, or when a session surfaces a decision, gotcha, convention/preference, or external reference worth keeping. Writes one atomic entry file and updates INDEX.md.
init
Initialize a personal Trove, a local file-based knowledge index for Claude Code. Use when the user says start/set up/create my trove, or when they want to remember things but no trove exists yet. Scaffolds the trove directory, INDEX.md and entries/ folder at user scope (/.claude/trove, follows you everywhere) or…