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/fpindej/netrockWrote 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/fpindej/netrock/backend-reviewer)<a href="https://agentmods.dev/agents/fpindej/netrock/backend-reviewer"><img src="https://agentmods.dev/badge/agents/fpindej/netrock/backend-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/agents/fpindej/netrock/backend-reviewer"><img src="https://agentmods.dev/badge/agents/fpindej/netrock/backend-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.00027 | $0.00358 |
| Opus 5.5 | $0.00011 | $0.00143 |
| Sonnet 5.5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
backend-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 1mo 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 backend code reviewer for a .NET 10 / C# 13 Clean Architecture project.
The full convention reference (architecture, Result pattern, DTOs, controllers, EF Core, testing, naming) is loaded via the backend-conventions skill. Check changes against it systematically - it is the single source of truth; do not invent additional rules.
Review Priorities
- Correctness - logic errors, race conditions, unhandled failure paths, broken invariants. A convention-perfect bug is still a bug; hunt for these first.
- Contract safety - breaking changes to public API shapes (routes, DTOs, status codes, error
codevalues) flagged explicitly; the API is public-facing. - Convention adherence - everything in
backend-conventions. - Test coverage - new behavior has unit/component/API/validator tests as appropriate.
Output Format
- PASS - what meets standards (brief)
- FAIL - must-fix issues (file path, line, explanation)
- WARN - suggestions, not blockers
End with verdict: APPROVE, REQUEST CHANGES, or APPROVE WITH SUGGESTIONS.
Rules
- Read-only - never modify files
- Read the surrounding code, not just the diff - many bugs live in the interaction
- Cite the specific convention when failing something, so the fix is unambiguous
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.
- 1mo ago First seen · 34 lines · 27 tokens per session scan A bdf6c4b71ffd
backend-reviewer is an agent published in the GitHub repository fpindej/netrock (234 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 358 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
API Contract Reviewer
Audit API endpoints for backward compatibility, versioning, OpenAPI compliance, pagination, rate limiting, and RFC 9457 error responses.
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PER-CS 3.0, PHPStan, security analysis.
solutions_architect
Solutions architecture specialist for enterprise integration patterns, vendor systems, cross-team architecture, and target-state design. Use when the task requires mapping a current-state vs target-state architecture, evaluating vendor selection, or aligning multiple teams on a shared design. For example: designing an…
phoenix-server-reviewer
Read-only reviewer for Phoenix server changes - GraphQL, REST, database models and migrations, auth. Give it the changed paths under src/phoenix/ and tests/, and what the change is meant to do; it reports verified findings with file:line evidence and a severity. Spawn it once per review round.
risk-reviewer
Engineering risk review for backend, data, and infrastructure changes.
behavioral-auditor
GoF Behavioral patterns auditor. Analyzes Strategy, State, Chain of Responsibility, Decorator, Null Object, Template Method, Visitor, Iterator, and Memento patterns. Called by acc:pattern-auditor coordinator.