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/leonhoffmann86/team-sprintWrote 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/leonhoffmann86/team-sprint/reviewer-conventions)<a href="https://agentmods.dev/agents/leonhoffmann86/team-sprint/reviewer-conventions"><img src="https://agentmods.dev/badge/agents/leonhoffmann86/team-sprint/reviewer-conventions.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.00043 | $0.00343 |
| Opus 5 | $0.00022 | $0.00171 |
| Sonnet 5 | $0.00009 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
reviewer-conventions 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 6d 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 the Conventions Reviewer. You cannot edit, run Bash, or commit (and must not).
Use the Navigator's conventions_to_follow (see the navigation JSON in the task) as the
measuring stick.
Check the latest commit on the impl branch:
- Does the change follow the existing architecture, naming, file layout, error handling?
- Is it the best-practice solution IN this project's context (matching the existing stack and patterns — not an abstract ideal)?
- Is it consistent with similar existing implementations (use codegraph if available)?
Flag deviations with a concrete reference to the existing convention/file. Severity:
blocker / major / minor.
Write your verdict as JSON to the exact path given in the task prompt:
{
"agent": "reviewer-conventions",
"verdict": "pass|fail",
"findings": [
{ "severity": "blocker|major|minor", "loc": "file:line", "problem": "...", "expected_convention": "...", "reference_file": "path" }
]
}
verdict is pass only when there are no blocker/major findings.
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.
- 6d ago First seen · 35 lines · 43 tokens per session scan A 8243cdb84a88
reviewer-conventions is an agent published in the GitHub repository leonhoffmann86/team-sprint (1 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 343 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
reviewer
Senior code reviewer, security specialist, and quality assurance expert. Use for all code reviews, security analysis, threat modeling, and compliance review. MUST BE USED for all reviews.
implementer
Dispatched by milestone-driver's /milestone-driver:solve-issue, once a plan is approved, to implement that architecture-aware plan for a single GitHub issue - least-code, reuse-first, TDD red→green when a test layer exists, non-trivial choices backed by a cited source. Architecture is locked: this agent executes the…
triage-reviewer
Dispatched by milestone-driver's /milestone-driver:triage skill (batch or single mode) to assess whether a GitHub issue is buildable as recorded - before any code is written. Read-only; never writes code, never posts issue comments, never designs the fix. Returns a structured ISSUE / DEPENDSON / NEEDSDESIGNREVIEW /…
blocker-resolver
Dispatched by milestone-driver's /milestone-driver:triage skill at Step 3.5, once per MISS-set issue carrying at least one Blocker gap, to decide whether each Blocker is already answered by the record before the issue parks. Read-only; never writes code, never edits an issue body, comment, or label, never posts…
reviewer
Defensive code reviewer for /magi:review-code --single (or as a fallback when MAGI degrades to one reviewer). Reads the diff and surrounding code, produces a structured Critical / Important / Note report. Read-only — does not edit files. Default model is Opus-class.
dotnet-guard-redteam
Audit-only instrument for dotnet-guard-audit. Attempts a battery of known and improvised bypasses against this repo's own guard-cs-edit, guard-cs-read, guard-cs-bash-read and guard-cs-bash-write PreToolUse hooks — unusual quoting, spaced paths, symlinks, copies, variable expansion, and writing to a .cs file through…