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 agentmods add skills/chipfighter/coding-discipline/verify-before-donenpx skills add chipfighter/coding-discipline --skill verify-before-donegit clone --depth 1 https://github.com/chipfighter/coding-disciplineWhat 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 | $0.00062 | $0.00663 |
| Opus 5 | $0.00031 | $0.00331 |
| Sonnet 5 | $0.00012 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
verify-before-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 3d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hard rule: Only evidence gathered after the last relevant change to the code, files, or environment, and directly sufficient to prove the claim, counts.
- Claiming completion without sufficient evidence = lying; running the full test suite for a typo = waste.
- You may reuse evidence just gathered, but state when it was gathered and confirm that no code was changed, nothing was pulled, and the environment was not modified afterward. If you cannot say for sure, check again.
Required checks (before any claim of success or completion)
- What claim must be proven? What check is just sufficient (command output / diff / artifact inspection…)?
- Was the evidence gathered after the last relevant change? Yes—state when. No / uncertain—check again.
- If you ran a command, read all output, inspect the exit code, and count failures. If you inspected a diff or artifact, state what you checked and the result.
- Does the evidence actually prove the claim? Yes—state the conclusion together with the evidence. No—report the true status.
Skipping any step = lying, not verification.
Could not run ≠ skipped
If a command cannot run (missing environment, broken dependencies, timeout), verification failed. Report that verification could not be completed and what blocked it. Do not quietly mark the step green as “skipped,” and do not misreport an environment problem as a product failure.
None of these counts as "verified"
| Claimed evidence | Why it does not count |
|---|---|
| lint / type checks passed | This proves only that the checks pass, not that the project builds, runs, or behaves correctly. |
| A subagent reported "success" | That is its claim. Inspect the diff / actual artifact yourself. |
| The regression test passed once | This does not prove it catches the problem. In a safe, isolated way, temporarily disable this round's fix → the test must fail → restore the fix → the test must pass. Do not do this by reverting or overwriting user files. |
| "Tests are green = requirements are met" | Check each requirement explicitly; green tests alone are not enough. |
| Only part of the suite ran | This does not mean the whole suite passed. |
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.
- 3d ago First seen · 36 lines · 62 tokens per session scan A 7e4e57f82c64
verify-before-done is a skill published in the GitHub repository chipfighter/coding-discipline (6 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 663 once invoked, about $0.0003 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
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
agent-workspace-linux
Use when a task needs an isolated hidden Linux desktop or workspace-owned browser: GUI app QA, web/browser/shopping automation, sandboxed app observation, or stale workspace cleanup. Routes agent-workspace-linux MCP tools on demand. Does NOT apply to host desktop/Chrome control, generic MCP setup, or pure code/file…
ss-component
Generate a new UI component following the StyleSeed design conventions.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-review
Interactive 4-section code review using monitor, predictor, and evaluator agents plus the user and maintainer role reviewers on current changes. Use when reviewing a diff, PR, or staged work before merge. Do NOT use to plan or implement; use map-plan or map-efficient.
runjam-defaults
Default constraints for every RunJam session. Defines output path conventions, dependency checking rules, fallback strategies, and file management discipline. This skill is auto-injected into every session — do not remove. Current session working directory: /Users/guizhan/work/code/runjam.