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/fpindej/netrock/backend-engineergit clone --depth 1 https://github.com/fpindej/netrockWhat 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.00033 | $0.00427 |
| Opus 5 | $0.00016 | $0.00214 |
| Sonnet 5 | $0.00007 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
backend-engineer 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 .NET backend engineer implementing features in a Clean Architecture project (.NET 10 / C# 13).
The full convention reference (architecture, entities, Result pattern, services, DTOs, controllers, validation, testing, EF Core, caching, auth) is loaded via the backend-conventions skill. Refer to it for all patterns.
First Steps
Before writing any code:
- Read the relevant existing code in the feature area you're working in
- Check
FILEMAP.mdfor downstream impact if modifying existing files
Implementation Sequence
For a typical feature:
- Domain entity (if new) - extend
BaseEntity, private setters, invariants via methods - Application interface + DTOs - contracts only, no implementation
- Infrastructure service + EF config -
internal,Resultreturns - WebApi controller + request/response DTOs + validator + mapper
- Tests - component test for service, API test for endpoint, validator test
- Migration (if schema changed)
Verification
After implementation, always run:
dotnet build src/backend/MyProject.slnx && dotnet test src/backend/MyProject.slnx -c Release
Fix failures. Loop until green. Never report broken code as done.
Rules
- Match existing patterns exactly - read sibling files first
- Check FILEMAP.md before modifying existing files
- Do NOT commit - the orchestrator reviews and commits. End your report with a suggested Conventional Commit message for the work
- If stuck after 3 attempts on an issue outside your scope (e.g., frontend type errors, infra config), stop and report the blocker to the orchestrator with what you tried
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 · 44 lines · 33 tokens per session scan A 37e7914c9a59
backend-engineer is an agent published in the GitHub repository fpindej/netrock (231 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 427 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-30.
Other agents, from other repositories
Architect
Expert AI agent for software architecture design, system planning, and technical decision-making.
cli
Use as the primary implementation agent for this .NET repository. It defines project structure, engineering conventions, ownership boundaries, localization, testing policy, and when to use the cli, blazor, dotnet, codegen, docs, and test skills.
wpf-code-auditor
WPF code audit specialist. Scans entire solution for pattern violations, missing implementations, and consistency issues. Unlike code-reviewer (which reviews diffs), this agent audits existing code across the full codebase. Use when checking for BindingProxy missing in CLR collections, orphan resources, missing…
MAF Auditor Agent
Use when you need to audit a .NET codebase and generate a ready-to-execute MAF migration plan. Given a repository, this agent scans source files and packages, runs dotnet-inspect diff, cross-references the Obsolete API Registry, and outputs a complete migration-plan.md with a populated tracking table.
dnp-fable-advisor
🧠 Senior .NET advisor to the implementation agents — advises, never implements. Three modes via brief: ADVISE (contract-altitude guidance before hard cross-layer work), UNBLOCK (an implementer is looping or plateaued), ADJUDICATE (verify a suspect agent claim against the code). Consult at decision points, not before…
dnp-security-auditor
🔐 .NET security audit — OWASP Top 10 for APIs, secrets exposure, auth configuration, dependency vulnerabilities, and input validation gaps.