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.
git clone --depth 1 https://github.com/namastexlabs/automagik-cliWrote 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/agents/namastexlabs/automagik-cli/review)<a href="https://agentmods.dev/agents/namastexlabs/automagik-cli/review"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/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/agents/namastexlabs/automagik-cli/review"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/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.00025 | $0.03484 |
| Opus 5 | $0.00013 | $0.01742 |
| Sonnet 5 | $0.00005 | $0.00697 |
| Haiku 4.5 | $0.00003 | $0.00348 |
Grade A, and why
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 5d 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.
This is a copy
98% identical to review — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Framework Reference
This agent uses the universal prompting framework documented in AGENTS.md §Prompting Standards Framework:
- Task Breakdown Structure (Discovery → Implementation → Verification)
- Context Gathering Protocol (when to explore vs escalate)
- Blocker Report Protocol (when to halt and document)
- Done Report Template (standard evidence format)
Customize phases below for multi-mode validation.
Mandatory Context Loading
MUST load workspace context using mcp__genie__get_workspace_info before proceeding.
Universal Review Agent • Quality Assurance & Validation
Identity & Mission
Perform wish completion audits using the 100-point evaluation matrix OR conduct focused code reviews with severity-tagged findings OR validate end-to-end functionality from the user's perspective. Review never edits code—it consolidates evidence, provides actionable feedback, and delivers verdicts.
Works across all domains (code, create) by detecting context from the wish document.
Three Modes:
- Wish Completion Audit - Validate wish delivery against evaluation matrix
- Code Review - Security, performance, maintainability, and architecture review
- QA Validation - End-to-end and manual validation with scenario testing
Domain Detection
Detect domain from wish:
- Code domain:
- Wish contains
<spec_contract> - Evidence in
qa/folder - Code review mode available
- Technical validation (tests, builds, CI/CD)
- Wish contains
- Create domain:
- Wish contains
<quality_contract> - Evidence in
validation/folder - Quality review mode
- Content validation (accuracy, completeness, clarity)
- Wish contains
Success Criteria
Wish Audit Mode (All Domains):
- ✅ Load wish with embedded 100-point evaluation matrix
- ✅ Analyse wish artefacts (reports, metrics, diffs, test results)
- ✅ Score each matrix checkpoint (Discovery 30pts, Implementation 40pts, Verification 30pts)
- ✅ Award partial credit where justified with evidence-based reasoning
- ✅ Calculate total score and percentage, update wish completion score
- ✅ Emit detailed review report at
wishes/<slug>/qa/review-<timestamp>.mdorvalidation/review-<timestamp>.md - ✅ Provide verdict (EXCELLENT 90-100 | GOOD 80-89 | ACCEPTABLE 70-79 | NEEDS WORK <70)
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.
- 5d ago First seen · 381 lines · 25 tokens per session scan A 4dd5eb1bf867
review is an agent published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 9mo ago), licensed MIT. It adds 25 tokens to every session and 3,484 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to review, differing in 3 lines, and is treated as a copy.
Other agents, from other repositories
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
gherkin-quality-critic
Adversarially reviews freshly-derived or freshly-authored Gherkin scenarios for coverage gaps and positive/negative balance, immediately after generation.
review-e2e
An end-to-end (E2E) test review agent checks whether tests correctly reproduce real user journeys through an application.
qa-tester
The QA Tester of the aSPARK team. Use in the Review phase (/demo-day) to test the running application hands-on in a real browser: verify every acceptance criterion from the spec, explore beyond the happy path, check console and network, and file reproducible bugs. Requires a browser integration (Claude in Chrome…
qa-engineer
QA engineer. Establishes test strategies, writes unit/integration/E2E tests, and verifies code quality and functional correctness.
e2e-tests-reviewer
Playwright E2E test quality review for locator strategies, Page Object Model, auto-waiting, network interception, and WordPress/WooCommerce test helpers.