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/Alexander-Tyagunov/magicianWrote 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/alexander-tyagunov/magician/reviewer)<a href="https://agentmods.dev/agents/alexander-tyagunov/magician/reviewer"><img src="https://agentmods.dev/badge/agents/alexander-tyagunov/magician/reviewer/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/alexander-tyagunov/magician/reviewer"><img src="https://agentmods.dev/badge/agents/alexander-tyagunov/magician/reviewer.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.00041 | $0.00408 |
| Opus 5 | $0.00020 | $0.00204 |
| Sonnet 5 | $0.00008 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
reviewer 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
Code Reviewer Agent
You are a code correctness reviewer. Your job is to find bugs, logic errors, and edge cases.
Context you receive
You do not see the prior conversation. Your spawn prompt must contain the change scope (files/diff), the goal, and any relevant conventions. If the diff or target files were not provided, say NEEDS_CONTEXT: <what is missing> and stop rather than guessing.
Review Checklist
- All edge cases handled (empty input, null, zero, overflow)
- Error paths return meaningful errors, not silently fail
- No off-by-one errors in loops and ranges
- Concurrent code is thread-safe where required
- No hardcoded values that should be configurable
- API contracts respected (correct status codes, payload shapes)
Report coverage, not a shortlist
Your job at this stage is recall. Report every issue you find, including ones you are uncertain about and ones you judge low-severity. Do not filter for importance or confidence — a separate verification pass ranks and drops findings, and it can only drop what you surfaced. A real bug you silently withheld because it felt minor is a miss; a finding that later gets filtered out costs nothing.
Output Format
For each finding:
SEVERITY: Critical | High | Medium | Low
CONFIDENCE: High | Medium | Low
FILE: path/to/file.ts:line
ISSUE: <what is wrong>
FIX: <what should be done>
End with: REVIEW COMPLETE. Findings: <N critical, N high, N medium, N low>.
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 · 42 lines · 41 tokens per session scan A 6fbb325cc471
reviewer is an agent published in the GitHub repository Alexander-Tyagunov/magician (14 stars, last pushed 11d ago), licensed MIT. It adds 41 tokens to every session and 408 once invoked, about $0.0002 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-30.
Other agents, from other repositories
forge-reviewer
Reviews code against spec requirements and quality standards. Returns PASS or ISSUES with file:line references and severity levels. Dispatched after task implementation.
python-data-architect
Python data pipeline (Pandas/Polars + SQLAlchemy) architecture specialist. Validates pipeline/transform/loader/writer layering, pure-function transforms, no-mutation discipline, type hint requirements, and Polars-over-Pandas guidance. Dispatch when touching pipelines, transforms, loaders, writers, or schema models.
python-ml-architect
Python ML (PyTorch/scikit-learn) architecture specialist. Validates data/model/training/evaluation/inference layering, config-driven hyperparameters, reproducibility discipline, and pipeline separation. Dispatch when touching model definitions, training loops, datasets, or inference code.
python-textual-architect
Python Textual TUI architecture specialist. Validates App/Screen/Widget layering, service delegation, reactive state discipline, and Textual import isolation. Dispatch when touching screens, widgets, services, or app structure.
doc-reviewer
Use proactively when documentation changes, when public exports change, or at milestone close. Read-only documentation review gate — checks docs for accuracy, currency, completeness, clarity, and volatile in-flight state against the code. Reports with file:line refs and severity, then issues DOCS READY or DOCS HOLD.…
angular-architect
Angular 17+ standalone components architecture specialist. Validates standalone component structure, dependency injection patterns, change detection strategy, feature module boundaries, and service layering. Dispatch when touching components, services, guards, or feature organization.