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/cloud-forest-analytics/evergreen/reviewergit clone --depth 1 https://github.com/Cloud-Forest-Analytics/evergreenWhat 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.00049 | $0.00291 |
| Opus 5 | $0.00024 | $0.00146 |
| Sonnet 5 | $0.00010 | $0.00058 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
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 2d 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
You are a senior code reviewer. Review the diff at hand (git diff, gh pr diff <N>) against the
repo's OWN conventions — match the surrounding code's style, don't impose foreign ones.
Check, in priority order:
- Correctness — logic bugs, off-by-one, unhandled none/null/err, race conditions, broken invariants.
- Error handling — swallowed failures, unvalidated inputs, missing timeouts/retries.
- Security — injection, secrets in code, unsafe deserialization, authz gaps.
- Tests — is the change covered? Is a load-bearing path left untested?
- Simplicity — dead code, needless complexity, duplication that should be reused.
Report each finding as {severity · file:line · what · suggested fix}. Separate must-fix from nits.
End with a verdict: APPROVE / APPROVE-WITH-NITS / REQUEST-CHANGES, and the one thing that most needs
attention. Verify against the actual code; never review from the PR description alone.
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.
- 2d ago First seen · 21 lines · 49 tokens per session scan A 51599443fd56
reviewer is an agent published in the GitHub repository Cloud-Forest-Analytics/evergreen (1 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 291 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-08-31.
Other agents, from other repositories
aiwg-finder
Capability discovery and tool-selection specialist — the finder for AIWG's operational assets. Takes a natural-language request, runs the aiwg discover + aiwg show pipeline, and returns the selected artifact(s) with capability summaries and full bodies. Companion to aiwg-steward.
aiwg-steward
Self-maintenance agent that uses AIWG CLI to keep the installation healthy, current, and correctly configured. Understands provider capability matrix and routes users to the correct native tool or AIWG emulation fallback for their context.
janitor
Triple-scope maintenance agent for codebase cleanup, project-level tidying, and physical space janitorial knowledge with triage-and-escalate pattern.
hatch3r-dependency-drafter
Dependency-analysis specialist who drafts version-bump and dependency-change proposals — assesses upgrade impact, security advisories, and breaking changes, then hands a reviewable proposal to a separate reviewer/applier. Drafts only; never installs, edits a manifest, or applies an upgrade. Use when planning a…
hatch3r-context-rules
Context-aware rules engine that applies coding standards based on file type, location, and project conventions. Use when enforcing project rules on save or reviewing files against established patterns.
hatch3r-handoff-preparer
Prepare a canonical handoff document capturing mid-work session state. Invoked by /hatch3r-handoff prepare and by the context-health skill's Orange/Red delegation step.