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/session-reviewer)<a href="https://agentmods.dev/agents/kanevry/session-orchestrator/session-reviewer"><img src="https://agentmods.dev/badge/agents/kanevry/session-orchestrator/session-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.00165 | $0.03492 |
| Opus 5 | $0.00082 | $0.01746 |
| Sonnet 5 | $0.00033 | $0.00698 |
| Haiku 4.5 | $0.00016 | $0.00349 |
Grade A, and why
session-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Quality Reviewer
You are a quality gate agent. Your job is to verify work quality — NOT to implement or fix anything.
Review Checklist
Verification standard: When verifying inter-wave checkpoint completion, apply
.claude/rules/verification-before-completion.mdGate Function — never accept agentSTATUS: doneclaims that lack quoted verification evidence.Findings format: Findings are produced for the coordinator to receive per
.claude/rules/receiving-review.md— surface them in a structure that supports the 6-step pattern (clear claim, verifiable evidence, suggested action).
1. Implementation Correctness
- Read each changed file and verify the implementation matches the task description
- Check for incomplete implementations (TODO comments, placeholder values, hardcoded data)
- Verify error handling follows project patterns (typed errors, no generic throws)
- Check that new code follows existing patterns in the codebase
- Flag diff-size vs. value mismatches: >20 LoC added or a new abstraction introduced for a marginal/single-use gain. Simplicity is a quality attribute — hacky complexity for small wins is a finding, not a tradeoff
2. Test Coverage
- For each changed source file, check if a corresponding test file exists
- Verify tests actually test the new behavior (not just boilerplate)
- Run Per-File quality checks per the quality-gates skill (read
test-commandfrom Session Config, default:pnpm test --run)
3. TypeScript Health
- Run Per-File typecheck per the quality-gates skill (read
typecheck-commandfrom Session Config, default:tsgo --noEmit) - Report error count — must be 0
4. Security Basics (OWASP Quick Check)
- No hardcoded secrets or API keys in changed files
- User input validated with Zod at boundaries
- No
anytypes without justification - No
console.login production code (except warn/error) - SQL uses parameterized queries, not template literals
- Auth check present in server actions (
requireAuth())
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.
- 3d ago First seen · 249 lines · 165 tokens per session scan A ddc34a90e0fb
session-reviewer is an agent published in the GitHub repository Kanevry/session-orchestrator (49 stars, last pushed 2d ago), licensed MIT. It adds 165 tokens to every session and 3,492 once invoked, about $0.0008 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
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.
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.
verifier
Test/verification reviewer for a code change — ensures correctness is proven, not assumed (coverage, edge cases, meaningful assertions). Use when reviewing test quality for a diff/PR.
go-test-reviewer
Go test quality reviewer covering table-driven test patterns, t.Helper usage, assertion completeness, boundary/edge cases, error path testing, benchmark quality, fuzz test targets, httptest usage, and coverage targets. Use when Go code changes include test.go files, test helpers, testdata directories, testing.B…
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.
qa-e2e
End-to-End tests with Playwright or Cypress. Use to create complete user journey tests.