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 makifbaysal/tasktrooper --skill verify-before-donegit clone --depth 1 https://github.com/makifbaysal/tasktrooperWrote 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/makifbaysal/tasktrooper/verify-before-done)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/verify-before-done"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/verify-before-done/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/makifbaysal/tasktrooper/verify-before-done"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/verify-before-done.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.00757 |
| Opus 5.5 | $0.00014 | $0.00303 |
| Sonnet 5.5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
verify-before-done scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Endpoint works (backend) | `curl` against the running service: status code and body | Code review of the handler | How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Before Completion
Overview
Claiming work is complete without verification is dishonesty, not efficiency.
Core principle: Evidence before claims, always.
The Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run the verification command in THIS run, you cannot claim it passes. A previous run, "should pass", or "looks correct" is not evidence.
The Gate Function
Before claiming any status or moving any task forward:
- IDENTIFY — what command proves this claim?
- RUN — execute the full command, fresh and complete.
- READ — the full output: exit code, failure count, warnings.
- VERIFY — does the output actually confirm the claim? If no: state the real status with evidence.
- ONLY THEN — make the claim, with the evidence.
Skipping any step is lying, not verifying.
What Each Claim Requires
| Claim | Requires | Not sufficient |
|---|---|---|
| Checks pass | The component's list_component_checks commands, run in this run, exit 0 — the hand-off gate runs exactly these |
A different command you picked yourself |
| Build succeeds | Build command: exit 0 | Linter passing, logs look fine |
| Bug fixed | Re-run the original symptom: passes | Code changed, assumed fixed |
| Regression test guards the fix | Revert the fix, run the test (MUST FAIL), restore, run again (passes) | The test passing once, with the fix already in place |
| Endpoint works (backend) | curl against the running service: status code and body |
Code review of the handler |
| Screen works (frontend) | browser_read_dom with contains: for the element, plus screenshots at the four widths |
A build that compiled |
| Screen works (mobile) | mobile_screenshot / mobile_read_ui, or the Flutter web-render fallback when no device is attached |
"The widget should render" |
| AC met | Line-by-line check of every acceptance criterion against what you just verified | Tests passing |
Tests passing is NOT the same as requirements met — re-read every acceptance criterion and confirm each one is actually satisfied.
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.
- 8d ago First seen · 73 lines · 36 tokens per session scan A 8bc765d50127
verify-before-done is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 757 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-05.
Other skills, from other repositories
triage-bug
Use when triaging a bug from session evidence (evidence-capture JSONL, replay JSONL, telemetry, repo-audit) instead of from a live user description, and producing a TDD fix plan plus a docs/bugs/{slug}.md triage artifact.
code-review
Use this skill to systematically review code changes for correctness, security, performance, maintainability, and test coverage. Activates after implementation, before merging, or when asked to review a pull request or code change. Produces a structured review report with findings categorized by severity.
tdd
Use this skill to practice test-driven development — writing tests before implementation, using tests to drive design, and validating implementation against pre-written tests. Activates when implementing new functionality, refactoring code, or fixing bugs where regression coverage is needed.
bug-diagnosis
Use this skill to systematically diagnose the root cause of a bug before attempting a fix. Activates when a bug is reported, a test is failing, or unexpected behavior is observed. Prevents guess-and-check debugging that introduces additional bugs while chasing symptoms.
qa-acceptance
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.