Borrowing it
Nothing to install: this file belongs to mohamedzhioua/agent-done-or-not. 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/mohamedzhioua/agent-done-or-not/main/AGENTS.mdgit 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/instructions/mohamedzhioua/agent-done-or-not/agents-md)<a href="https://agentmods.dev/instructions/mohamedzhioua/agent-done-or-not/agents-md"><img src="https://agentmods.dev/badge/instructions/mohamedzhioua/agent-done-or-not/agents-md/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/instructions/mohamedzhioua/agent-done-or-not/agents-md"><img src="https://agentmods.dev/badge/instructions/mohamedzhioua/agent-done-or-not/agents-md.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.00309 | $0.00309 |
| Opus 5 | $0.00154 | $0.00154 |
| Sonnet 5 | $0.00062 | $0.00062 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
agent-done-or-not AGENTS.md 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
Proof-of-Done Rule (agent-done-or-not)
Applies to any agent operating in this repo (Codex, and other harnesses that
read AGENTS.md).
Before reporting a task complete, you MUST verify it through the proof gate. Claiming "done" without a passing receipt is not allowed.
-
Run the verifying command through the gate:
bash done-gate.sh capture --label check -- <your verifying command>It records the command, its exit code, and a SHA-256 of the output, and exits with the command's own code — so a failing check fails here.
-
Only report completion after a PASSING receipt.
-
If the check fails, fix the code and capture again. Never report success on a red check.
Claim markers (for audit)
When you assert a check passed, also emit a claim marker in your final summary so
done-gate.sh audit can diff the claim against the receipt ledger:
<agent-done:claim label="test" exit="0" />
Use the same --label you passed to capture; omitting exit asserts a pass.
An unbacked marker is caught by audit. Full contract and paste-ready
instruction: docs/markers.md.
See examples/install.md for wiring a hard stop-gate where your harness
supports stop/finish hooks.
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 · 36 lines · 309 tokens per session scan A 24757d2fa269
agent-done-or-not AGENTS.md is an instructions file published in the GitHub repository mohamedzhioua/agent-done-or-not (6 stars, last pushed 1mo ago), licensed MIT. It adds 309 tokens to every session, about $0.0015 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.