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 mohamedzhioua/agent-done-or-not --skill done-or-notgit clone --depth 1 https://github.com/mohamedzhioua/agent-done-or-notWrote 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/mohamedzhioua/agent-done-or-not/done-or-not)<a href="https://agentmods.dev/skills/mohamedzhioua/agent-done-or-not/done-or-not"><img src="https://agentmods.dev/badge/skills/mohamedzhioua/agent-done-or-not/done-or-not/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/mohamedzhioua/agent-done-or-not/done-or-not"><img src="https://agentmods.dev/badge/skills/mohamedzhioua/agent-done-or-not/done-or-not.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.00111 | $0.01420 |
| Opus 5 | $0.00056 | $0.00710 |
| Sonnet 5 | $0.00022 | $0.00284 |
| Haiku 4.5 | $0.00011 | $0.00142 |
Grade C, and why
done-or-not 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 12d 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.
| One-liner installer | `curl -fsSL https://raw.githubusercontent.com/mohamedzhioua/agent-done-or-not/main/install.sh \| sh` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
(tests, build, lint, curl) through a tamper-evident gate that records the How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
done-or-not
Why this exists
AI agents routinely announce tasks are complete without verifying anything
actually ran. This skill enforces a proof gate: the agent must run the real
check (tests, build, typecheck, lint, a curl against the endpoint — whatever
demonstrates the claim), record a tamper-evident receipt, and only then may it
report done.
The gate records: the command, its exit code, and a SHA-256 of its full
output. Freshness is judged by the epoch inside the receipt (not file mtime,
which touch could forge). A receipt can only clear one stop — it is consumed
on use.
When to use
Use whenever you are about to tell the user that a task, build, test, fix, or verification step is finished. A completion claim requires proof from the gate, not confidence or memory.
How to use
Portable skill command
-
Identify the command that verifies the work. Choose the smallest check that actually verifies the claim: tests, build, typecheck, lint, a
curlagainst a running endpoint, or another command with meaningful pass/fail behavior. -
Run the verifying command through the proof gate. This works even when this skill was installed without the repo-root gate scripts:
npx agent-done-or-not capture --label check -- <your verifying command>If the protected repo was initialized with local scripts, these faster local forms are also valid:
bash done-gate.sh capture --label check -- <your verifying command> pwsh -File done-gate.ps1 capture --label check -- <your verifying command>The gate records the command, its exit code, and a SHA-256 of the output. It exits with the command's own code, so a failing check fails the capture.
-
Only report the work complete after a fresh PASSING receipt exists.
-
If the check fails, fix the problem and capture again. Never report success on a red check.
Windows (native PowerShell — no bash required)
npx agent-done-or-not capture --label check -- <your verifying command>
pwsh -File done-gate.ps1 capture --label check -- <your verifying command>
# or, on Windows PowerShell 5.1:
powershell -NoProfile -File done-gate.ps1 capture --label check -- <your verifying command>
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.
- 12d ago First seen · 168 lines · 111 tokens per session scan C e574b88da309
done-or-not is a skill published in the GitHub repository mohamedzhioua/agent-done-or-not (6 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 1,420 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
quality-gate
Use when you need to check if current work meets quality thresholds before proceeding to the next phase or merging.
verification-before-completion
Use when claiming task completion or marking items as done. Covers completion evidence requirements, verification methods, and anti-rationalization patterns.
verification-loop
6-stage automated verification pipeline producing READY/NOT READY verdict.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
operational-value-designer
Design and verify a deterministic operational-value grader for a GitHub Agentic Workflow. Use for per-run operational value, evidence attribution, maturation, baselines, and operational-value evaluators. Usage: /operational-value-designer OWNER/REPO WORKFLOW-NAME.