Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-hive. 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/namastexlabs/automagik-hive/main/.claude/commands/wish-review.mdgit clone --depth 1 https://github.com/namastexlabs/automagik-hiveWrote 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/namastexlabs/automagik-hive/wish-review)<a href="https://agentmods.dev/commands/namastexlabs/automagik-hive/wish-review"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-hive/wish-review/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/namastexlabs/automagik-hive/wish-review"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-hive/wish-review.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.00000 | $0.00614 |
| Opus 5 | $0.00000 | $0.00307 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
wish-review 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 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.
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
/wish-review – Wish Completion Audit
description: Execute an end-to-end review loop for a wish, combining test execution, Death Testament aggregation, and scoring.
[CONTEXT]
- Designed for branches where multiple forge tasks have landed and the wish is nearing closure.
- Runs a standardized audit so humans can iterate until the wish earns a 100/100 readiness score.
- Operates outside the sandbox: command may trigger UV tests, diff inspection, and report generation.
[SUCCESS CRITERIA]
✅ Parses the wish file for status, success criteria, and linked artefacts.
✅ Aggregates latest commits plus Death Testament references into the audit report.
✅ Executes each --tests command (default set provided below) via uv run … and captures pass/fail.
✅ Emits a structured review summary, including completion score (0–100), blockers, and next-step recommendations.
✅ Records evidence paths (wish, forge plan, DTs, test logs) for traceability.
[DEFAULT TEST MATRIX]
uv run pytest tests/lib/auth/test_credential_service.py -quv run pytest tests/integration/auth/test_single_credential_integration.py -quv run pytest tests/cli/test_docker_manager.py -q
[COMMAND SIGNATURE]
/wish-review @path/to/wish.md \
[--tests "<command>"]... \
[--score-only]
- Required first argument: wish file, referenced with
@so the report can link back. --testsmay be repeated to override or extend the default matrix.--score-onlyskips command execution and recomputes score using cached results (for fast follow-up after minor doc edits).
[OUTPUT]
- Human-readable report (markdown) summarizing:
- Wish metadata (status, phases, success criteria)
- Commits since last review (with task IDs)
- Test results table (pass/fail + command output snippet)
- Completion score (0–100) with rubric: implementation, validation, outstanding risks
- Recommended follow-up forge tasks (auto-generated when score < 100)
- Optional JSON payload for scripts integrating with future automation.
[PROCESS BREAKDOWN]
- Discovery – Load wish, forge plan, and latest Death Testaments; compute change summary.
- Validation – Run queued test commands (unless
--score-only), capture logs. - Scoring – Apply rubric; highlight blockers and residual risks.
- Recommendation – Suggest new forge task groups or close-out actions based on score.
- Report – Emit markdown + JSON (under
tmp/wish-review-<timestamp>.json).
[NOTES]
- Always use
uv run …for Python tooling. - Completion score of 100/100 requires: all success criteria met, tests passing, no unresolved risks.
- When blockers exist, include evidence and reference any new Forge tasks created in response.
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 · 54 lines · 0 tokens per session scan A 76325972c340
wish-review is a command published in the GitHub repository namastexlabs/automagik-hive (24 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 614 tokens. 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-30.
Other commands, from other repositories
os-up
A command that checks and starts the AI Team OS API server and dashboard. An API server provides data and operations to other programs, while a dashboard is a web interface for viewing and using the system.
os-status
A command for viewing the current state of an AI Team OS project, including teams, agents, and active meetings.
os-task
A command for managing an AI Team OS task wall: viewing tasks, adding new work, and checking task details and progress.
os-help
A command that displays the available AI Team OS slash commands and explains what each one does. Slash commands are short commands beginning with `/` that trigger specific actions.
os-meeting
A command for listing active AI Team OS meetings, creating a meeting, or viewing a meeting’s messages and details.
os-hooks
A command for checking and repairing Claude Code Hooks, which are scripts Claude Code runs when certain events happen. It checks the global hook settings, the repository definitions, and the installed runtime scripts.