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.
git clone --depth 1 https://github.com/Kanevry/session-orchestratorWrote 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/kanevry/session-orchestrator/project-code-review)<a href="https://agentmods.dev/agents/kanevry/session-orchestrator/project-code-review"><img src="https://agentmods.dev/badge/agents/kanevry/session-orchestrator/project-code-review/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/agents/kanevry/session-orchestrator/project-code-review"><img src="https://agentmods.dev/badge/agents/kanevry/session-orchestrator/project-code-review.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.00000 | $0.00213 |
| Opus 5 | $0.00000 | $0.00106 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
project-code-review 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 5d 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
Project Code Review Agent
Performs read-only review of code changes. Use this agent to:
- Enforce project-specific coding conventions
- Identify security issues, injection risks, or unsafe patterns
- Check for missing error handling or edge cases
- Verify adherence to naming conventions and file structure
Edit this file to add project-specific review checklists, e.g. banned patterns, required linting rules, security invariants, or architecture constraints.
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.
- 5d ago First seen · 19 lines · 0 tokens per session scan A 82c8d274e612
project-code-review is an agent published in the GitHub repository Kanevry/session-orchestrator (50 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 213 tokens. 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
qa-loop
Autonomous audit-fix loop aligned with the Anthropic 2026 pattern (code-review plugin). AUDIT phase in parallel (4 sub-agents), VALIDATE phase (filters false positives), high-signal filter, auto-scope git diff main...HEAD. Flags --audit-only and --comment for read-only and inline PR post modes.
qa-claudemd
Audit of compliance with the project's CLAUDE.md and repo conventions. Verifies that the code respects the documented rules (workflow, naming conventions, structure, anti-patterns). Use as a sub-agent in qa-loop for the Anthropic 2026 pattern.
arbiter
Aggregates the refuter panel's independently-committed verdicts into one per-criterion verdict, under the independence guard. Never itself judges the diff. Invoked only by mnm-verify, after every lens for the current round has already committed.
refuter-correctness
Breaks a diff on pure functional correctness — wrong output, crash, violated invariant, uncovered edge case. Read-only, re-runs the decisive check itself. Invoked only by mnm-verify; never by the user, never by the implementer.
refuter-regression
Breaks a diff on regression — anything that worked before this change and doesn't now, including quietly weakened checks. Read-only, re-runs the pass-to-pass suite itself. Invoked only by mnm-verify; never by the user, never by the implementer.
refuter-spec
Breaks a diff on spec-conformance — DoD criteria met in letter but not substance, Non-Goals silently crossed, write-scope exceeded. Read-only. Invoked only by mnm-verify; never by the user, never by the implementer.