Borrowing it
Nothing to install: this file belongs to ManSio/mscodebase-intelligence. 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/ManSio/mscodebase-intelligence/main/.opencode/command/done.mdgit clone --depth 1 https://github.com/ManSio/mscodebase-intelligenceWrote 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/commands/mansio/mscodebase-intelligence/done)<a href="https://agentmods.dev/commands/mansio/mscodebase-intelligence/done"><img src="https://agentmods.dev/badge/commands/mansio/mscodebase-intelligence/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/commands/mansio/mscodebase-intelligence/done"><img src="https://agentmods.dev/badge/commands/mansio/mscodebase-intelligence/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.00017 | $0.00449 |
| Opus 5.5 | $0.00007 | $0.00180 |
| Sonnet 5.5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
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 26d 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
You are running the DONE phase. The value of this phase is entirely in what it refuses to claim.
Before claiming done
python tools/verification/run_all.py
python -m pytest tests/ -q
git status --short
A green suite does not mean the task is done. It means the guards still work.
The honesty rules
- Every number needs a referent: a command, a path, an id, a hash. A number you
cannot regenerate today is
measured on <sha>, superseded by X— not restated. ✅requires saying where it was verified.✅ verified on origin/main,⚠️ committed, not pushed,⚠️ changed, not runtime-tested,❓ reported, not confirmed. Pick one; there is no unmarked ✅.- List what is still open. An honest "3 of 9 open" beats a false "done".
- If something was reverted, say so and why. Side effects of your own operations do not stay silently in the diff.
- Do not soften a refutation into a partial win. If the hypothesis failed, say it failed.
Output
## [🏁 ИТОГ] <task>
1. What changed (2-4 lines, verbs)
2. Hypothesis / command / raw output / verdict
3. Files changed, and why each
4. Pitfalls hit
5. Numbers: measured by <command>, or "not measured"
6. DoD: what is closed, what is not
7. Verified from clean state: yes/no + how
8. Open items
9. How to check it yourself
Final check
If the honest version of this report is uncomfortable, that is the correct version. A completion report is the last place where overclaiming is still possible, and therefore the first place a future reader will look to decide whether to trust you.
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.
- 26d ago First seen · 51 lines · 17 tokens per session scan A fd46613cd5f9
done is a command published in the GitHub repository ManSio/mscodebase-intelligence (3 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 449 once invoked, about $0.0001 per session on Opus 5.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-10-04.
Other commands, from other repositories
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
ship
A release command for preparing code changes as separate Git commits, creating release notes, and adding a version tag. Git is a system for tracking code changes, and a tag marks a specific release.
fix-tests-execute
Phase 2 of fixing-tests: Fix Execution - investigate, classify, fix, verify, and commit each work item.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.
build
A command for carrying out the next unfinished coding task from a plan, including writing tests, implementing the change, checking the project, and committing it. TDD, or test-driven development, means writing a failing test before the code that makes it pass.