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 skills add PralhadYadawad/avvarre --skill avvarre-reviewergit clone --depth 1 https://github.com/PralhadYadawad/avvarreWrote 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/skills/pralhadyadawad/avvarre/avvarre-reviewer)<a href="https://agentmods.dev/skills/pralhadyadawad/avvarre/avvarre-reviewer"><img src="https://agentmods.dev/badge/skills/pralhadyadawad/avvarre/avvarre-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/skills/pralhadyadawad/avvarre/avvarre-reviewer"><img src="https://agentmods.dev/badge/skills/pralhadyadawad/avvarre/avvarre-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.00022 | $0.00153 |
| Opus 5 | $0.00011 | $0.00077 |
| Sonnet 5 | $0.00004 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
avvarre: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
Avvarre reviewer
Use this workflow for a thorough review of changed files or a user-selected scope.
Run avvarre_pr for a change-set review, or use avvarre_file for a named file. Triage findings critical-to-low, explain only actionable findings, and preserve application behavior when making requested fixes. For naming violations, use the #rename tool for safe project-wide renames. Re-run Avvarre after each changed file. When project memory exists, update .avvarre/tasks.md only for work actually completed and only when the user has authorized the edits.
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 · 11 lines · 22 tokens per session scan A 5ee3aef62b85
avvarre:reviewer is a skill published in the GitHub repository PralhadYadawad/avvarre (4 stars, last pushed 16d ago), licensed MIT. It adds 22 tokens to every session and 153 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-31.
Other skills, from other repositories
moai-ref-cross-model-audit
Cross-model audit convergence reference for the plan-auditor and sync-auditor agents. Documents how to invoke the auditmulti MCP tool to fan a code review out across the codex and GLM (z.ai) backends in parallel, converge their verdicts with the in-session Claude verdict, and fold the resulting per-backend verdicts +…
moai-foundation-quality
TRUST 5 quality principles and how MoAI enforces them through agents, the 3-level harness, /moai gate, and sync-auditor scoring. Use for code review, quality gate checks, coverage targets, or TRUST 5 compliance.
code-reviewer
Automatic code quality and best practices analysis. Use proactively when files are modified, saved, or committed. Analyzes code style, patterns, potential bugs, and security basics. Triggers on file changes, git diff, code edits, quality mentions.
ase-arch-analyze
Review software architecture, including package cohesion and inter-package coupling.
ase-code-lint
Lint source code for potential code quality problems. Use when the user wants to "lint" or "check" source code.
ase-code-analyze
Analyze the source code for problems in either the logic and semantics and its related control flow, performance and efficiency, or security.