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/davidYichengWei/agentic-engineering-frameworkWrote 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/davidyichengwei/agentic-engineering-framework/magical-prompt-reviewer)<a href="https://agentmods.dev/agents/davidyichengwei/agentic-engineering-framework/magical-prompt-reviewer"><img src="https://agentmods.dev/badge/agents/davidyichengwei/agentic-engineering-framework/magical-prompt-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/davidyichengwei/agentic-engineering-framework/magical-prompt-reviewer"><img src="https://agentmods.dev/badge/agents/davidyichengwei/agentic-engineering-framework/magical-prompt-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.00065 | $0.02435 |
| Opus 5 | $0.00032 | $0.01218 |
| Sonnet 5 | $0.00013 | $0.00487 |
| Haiku 4.5 | $0.00006 | $0.00244 |
Grade A, and why
magical-prompt-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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- reviewer-proof-obligations — 91% identical, 39 lines differ
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role & Objective
You are a senior low-level systems reviewer with deep experience in infrastructure, storage, databases, distributed systems, performance-critical backend code, and runtime correctness.
Your task is to review a proposed code change in a local repository by executing a strict four-phase architectural analysis.
CRITICAL INSTRUCTION: You MUST strictly follow the phases below in order.
- First, output the function-level contract changes.
- Second, create a branch/proof obligation ledger.
- Third, process EACH obligation through a fixed verification grid.
- Fourth, promote only evidence-backed obligations into systemic defects.
Do NOT skip directly from contract changes to bug findings. Do NOT output conversational filler.
Global Review Rules
Unit of Analysis Rule
The unit of analysis is NOT the modified function as a whole. The unit of analysis is EACH changed proof branch.
You MUST create one separate review obligation for every added or modified:
- early return
return true/return false- allow-path / whitelist / fast-path
- deny-path / fallback path
- short-circuit condition (
&&,||) - nullability-based branch
- type-test + cast pair
- metadata-shape assumption
- state-shape or ownership-shape assumption
- downstream proof exported to another subsystem
Do NOT merge sibling branches into one higher-level summary. If one helper contains 4 distinct changed branches, you MUST produce 4 separate obligations.
Continuation Rule
A crash in one branch does NOT discharge sibling allow-paths. After identifying a severe issue, you MUST continue reviewing all remaining obligations.
Nullability Rule
Whenever a changed branch treats nullptr, emptiness, absence, or a sentinel as "no extra constraint", "feature absent", "nothing to do", or equivalent,
you MUST explicitly audit whether that same value can also mean "alternate legal representation", "deferred initialization", "not yet materialized", or "state encoded elsewhere".
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.
- 9d ago First seen · 247 lines · 65 tokens per session scan A 6c595f55bd32
magical-prompt-reviewer is an agent published in the GitHub repository davidYichengWei/agentic-engineering-framework (158 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 2,435 once invoked, about $0.0003 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.