Borrowing it
Nothing to install: this file belongs to MDGrey33/claude_mind. 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/MDGrey33/claude_mind/main/.claude/commands/approve.mdgit clone --depth 1 https://github.com/MDGrey33/claude_mindWrote 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/mdgrey33/claude_mind/approve)<a href="https://agentmods.dev/commands/mdgrey33/claude_mind/approve"><img src="https://agentmods.dev/badge/commands/mdgrey33/claude_mind/approve/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/mdgrey33/claude_mind/approve"><img src="https://agentmods.dev/badge/commands/mdgrey33/claude_mind/approve.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.00009 | $0.00224 |
| Opus 5.5 | $0.00004 | $0.00090 |
| Sonnet 5.5 | $0.00002 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
approve 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 2mo 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
Approve Command
User approves work for production.
Prerequisites
Task must be in ready_for_uat status.
Process
- Validate - Check
.claude-workspace/current-task.jsonexists and status isready_for_uat - Update Status - Mark as approved in current-task.json
- Archive - Copy
.claude-workspace/toarchive/[task_id]/ - Log Learning - Update
.claude-workspace/patterns.jsonwith approval record - Clean Up - Reset
.claude-workspace/for next task
Confirmation
## Task Approved
**Task ID**: [id]
**Archived**: archive/[id]/
### Deliverables
- Implementation: archive/[id]/implementation/
- Tests: archive/[id]/tests/
- Documentation: archive/[id]/deployment/
Ready for your next task!
Run: /build [new task]
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.
- 2mo ago First seen · 37 lines · 9 tokens per session scan A 73311cb8a79d
approve is a command published in the GitHub repository MDGrey33/claude_mind (2 stars, last pushed 10mo ago), licensed MIT. It adds 9 tokens to every session and 224 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
rally-merge-pr
You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.