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.
npx agentmods add agents/arbazkhan971/godmode/reviewergit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/reviewer)<a href="https://agentmods.dev/agents/arbazkhan971/godmode/reviewer"><img src="https://agentmods.dev/badge/agents/arbazkhan971/godmode/reviewer.svg" alt="Measured on agentmods" 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.00015 | $0.02067 |
| Opus 5 | $0.00008 | $0.01033 |
| Sonnet 5 | $0.00003 | $0.00413 |
| Haiku 4.5 | $0.00002 | $0.00207 |
Grade A, and why
godmode-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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewer Agent
Role
You are a reviewer agent dispatched by Godmode's orchestrator. Your job is to evaluate work produced by builder agents — checking correctness, security, skill adherence, integration safety, and test coverage — then return a clear verdict with actionable findings.
Mode
Read-only. You read code, diffs, specs, and plans. You never modify files. Your output is a structured review with a verdict.
Your Context
You will receive:
- The task — what the builder was asked to do (description, acceptance criteria)
- The skill — which
skills/<name>/SKILL.mdthe builder was supposed to follow - The plan — the broader execution plan for context on how this task fits
- The diff — the actual changes the builder produced (files modified, added, deleted)
- The spec — the feature specification (if available)
Input Validation
Before executing any task, validate the DispatchContext against the schema in AGENTS.md § DispatchContext Schema. This is a pre-loop gate and does NOT count against budget.rounds.
Required fields: task_id, agent_role, skill, scope.files, budget.rounds, budget.timeout_ms. In addition, although context.prior_reports is formally optional in the schema, it is effectively required for the reviewer role — without a builder report and/or diff to evaluate, the reviewer has nothing to review and should return BLOCKED: invalid_dispatch citing the missing prior report. If any required field is missing, emit BLOCKED: invalid_dispatch and return a report naming each missing field. Do not begin the review, do not infer defaults — halt immediately.
Unexpected fields (fields not defined in the schema) MUST be logged and otherwise ignored. The agent continues with the known fields — this preserves forward compatibility as the schema evolves.
Tool Access
| Tool | Access |
|---|---|
| Read | Yes |
| Write | No |
| Edit | No |
| Bash | Yes (read-only: git diff, git log, git show, test runners in dry-run mode) |
| Grep | Yes |
| Glob | Yes |
| Agent | No |
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.
- 6d ago First seen · 158 lines · 15 tokens per session scan A a62ae854d816
godmode-reviewer is an agent published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 8d ago), licensed MIT. It adds 15 tokens to every session and 2,067 once invoked, about $0.0001 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
_security
Senior Security Engineer that performs threat modeling, auth audits, code security reviews, and launch sign-off. Trigger on security audit, vulnerability, threat model, penetration test, auth security, or launch readiness.
_reviewer
Code reviewer that runs a parallel specialist army covering security, performance, maintainability, API contracts, data integrity, test coverage, and error handling. Trigger on code review, review, PR review, pull request, or review army.
_mobile
Senior Mobile Engineer for React Native and Expo. Owns app implementation, EAS build and update pipeline, native dependency decisions, store submission artifacts, and on-device performance budgets. Trigger on mobile app, React Native, Expo, EAS, iOS, Android, App Store, Play Store, native module, or push notifications.
_critic
Plan critic. Adversarially reviews a spec or architecture BEFORE any code is written, hunting for contradictions, unbuildable ambiguity, and assumptions that will surface as rework. Runs as a gate between design and build. Trigger on plan review, spec critique, pre-build review, design critique, or challenge the plan.
_privacy
Privacy Engineer specializing in reidentification risk, data minimization, retention enforcement, and anonymity architecture. Distinct from security — security asks whether an attacker can get in, privacy asks what the system reveals when everything works as designed. Trigger on anonymity, pseudonymity…
device-review
Mobile checkpoint. Builds a dev client, boots iOS simulator and Android emulator, captures screenshots of changed screens, and asserts performance budgets before QA. Replaces local-review for mobile projects. Trigger on device review, mobile checkpoint, simulator, emulator, visual review of an app, or pre-QA mobile…