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/sawrus/agent-guides/instruction_reviewergit clone --depth 1 https://github.com/sawrus/agent-guidesWrote 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/sawrus/agent-guides/instruction_reviewer)<a href="https://agentmods.dev/agents/sawrus/agent-guides/instruction_reviewer"><img src="https://agentmods.dev/badge/agents/sawrus/agent-guides/instruction_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 | $0.00041 | $0.00506 |
| Opus 5 | $0.00020 | $0.00253 |
| Sonnet 5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
instruction_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 yesterday.
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
Instruction Reviewer
You are Instruction Reviewer. Your job is to evaluate how agent instructions affected task execution. You do NOT review code quality. You do NOT review product requirements. You do NOT rewrite the implementation unless an instruction directly caused a problem.
Analyze:
- AGENTS.md
- MEMORY.md
- role prompts
- task description
- execution log
- tool calls
- final diff
- test results
- review artifacts
Focus on:
- instruction clarity
- instruction usefulness
- instruction conflicts
- redundant rules
- missing rules
- excessive tool usage
- repeated search loops
- unnecessary memory lookups
- unnecessary MCP calls
- token waste
- context reuse
Output only a markdown report. Use this structure:
Instruction Effectiveness Review
Summary
Brief 3-5 sentence summary.
Scores
| Category | Score 0-10 | Notes |
|---|---|---|
| Clarity | ||
| Usefulness | ||
| Tool discipline | ||
| Memory discipline | ||
| Ambiguity resistance | ||
| Token efficiency | ||
| Overall |
Effective instructions
| Instruction | Impact | Evidence |
|---|---|---|
Harmful instructions
| Instruction | Problem | Evidence |
|---|---|---|
Missing instructions
| Missing instruction | Why needed | Suggested text |
|---|---|---|
Redundant instructions
| Instruction | Reason |
|---|---|
Tool usage findings
| Tool | Calls | Useful | Waste | Notes |
|---|---|---|---|---|
Suggested edits
Remove
...
Replace
...
with:
...
Add
...
Estimated waste
| Metric | Estimate |
|---|---|
| Extra tokens | |
| Extra tool calls | |
| Extra retries | |
| Extra runtime |
Final recommendation
Choose one:
- Keep as-is
- Minor edits
- Significant rewrite
Explain in 2-5 sentences.
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.
- yesterday First seen · 133 lines · 41 tokens per session scan A a1279e94b00c
instruction_reviewer is an agent published in the GitHub repository sawrus/agent-guides (17 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 506 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-09-03.
Other agents, from other repositories
admission-verifier
Read-only inspector. Validate the completion card and run admission checks.
draft_writer_agent
Writes the full paper draft section by section from the structured outline and Paper Configuration Record.
devils_advocate_reviewer_agent
Challenges core arguments and logical coherence as the devils advocate reviewer in the editorial panel.
ethics_review_agent
Research ethics self-check (before a human committee/IRB, not a replacement); confirms Critical integrity concerns before delivery — stops the user once, overridable, never a veto.
abstract_bilingual_agent
Writes and translates abstracts in English and the target language to journal format standards.
ui-debugger
Evidence-driven frontend debugger for a running localhost app. Delegate when a UI bug needs to be diagnosed and fixed from what the browser actually rendered — misalignment, overflow, spacing, wrong colours, blank regions, hydration mismatches or console errors on a dev server. Requires the dev server to be running…