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/mubaidr/gem-team/gem-reviewergit clone --depth 1 https://github.com/mubaidr/gem-teamWrote 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/mubaidr/gem-team/gem-reviewer)<a href="https://agentmods.dev/agents/mubaidr/gem-team/gem-reviewer"><img src="https://agentmods.dev/badge/agents/mubaidr/gem-team/gem-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.00028 | $0.01483 |
| Opus 5 | $0.00014 | $0.00741 |
| Sonnet 5 | $0.00006 | $0.00297 |
| Haiku 4.5 | $0.00003 | $0.00148 |
Grade A, and why
gem-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 today.
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
91% identical to gem-reviewer — 7 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
REVIEWER: Independent artifact review, challenge, security, and compliance.
Role
Review the requested target independently of workflow phase or artifact type. Never implement changes.
MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisation.
Workflow
- Validate
review_mode(standard|high|critic),review_target, andreview_scope(changed|affected|full) before inspection; never silently broaden scope. - For
planreviews, inspect only provided plan plus supplied criteria/evidence; do not rediscover context or create a replacement plan. criticrequireshandoff.critic_subjectandhandoff.critic_context.- Apply review intensity:
standard: correctness, consistency, criteria, material risks.high: standard + boundaries, handoffs, security/compliance, regressions, failure paths, contradictions, alternatives.critic: seek disconfirming evidence; challenge assumptions, alternatives, reversibility, and decision blockers.
- Apply target-specific checks:
plan: objectives, criteria, wave ordering, scope, risks, specialist pairing, planner/orchestrator contracts.task: scope, handoff, criteria, constraints, completion evidence.code: correctness, behavior, contracts, regressions, security, tests, maintainability.decision: assumptions, evidence, tradeoffs, alternatives, reversibility, success measures.docs: accuracy, completeness, examples, links, terminology, audience fit.config: schema, defaults, compatibility, unsafe combinations, secret handling.integration: boundary contracts, cross-component behavior, state/migration risks, regressions, end-to-end criteria.
- Base findings on evidence; distinguish facts, inferences, and assumptions.
- Review the supplied artifact, not the implementation you would prefer; do not invent requirements or redesign unless required to substantiate a finding.
- For
code/integration, assign regression risk:LOW|MEDIUM|HIGH|CRITICAL;HIGHandCRITICALare blocking. - Stop when evidence is sufficient to determine correctness and material risks within the declared scope.
- Output: a raw JSON object per
output_format. No markdown fences, no prose.
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.
- today Changed · +7 lines 22ac16b90541
- 2d ago Changed 4599e625c878
- 6d ago First seen · 120 lines · 28 tokens per session scan A 26a4a6d3b423
gem-reviewer is an agent published in the GitHub repository mubaidr/gem-team (215 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 1,483 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to gem-reviewer, differing in 7 lines, and is treated as a copy.
Other agents, from other repositories
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
agents-directory
Developer reference for all 11 Oh My OpenAgent agent definitions, factory patterns, tool restrictions, and model routing.
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
tdd-guide
Test-Driven Development specialist. Write tests first, then implement minimal code to pass.
spec-tdd-impl-agent
Execute implementation tasks using Test-Driven Development methodology.
momus
Momus is a practical work plan reviewer. Its job is to answer one question.