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/fullstack-engineer)<a href="https://agentmods.dev/agents/fpindej/netrock/fullstack-engineer"><img src="https://agentmods.dev/badge/agents/fpindej/netrock/fullstack-engineer/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/fullstack-engineer"><img src="https://agentmods.dev/badge/agents/fpindej/netrock/fullstack-engineer.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.00043 | $0.00682 |
| Opus 5.5 | $0.00017 | $0.00273 |
| Sonnet 5.5 | $0.00009 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
fullstack-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 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior fullstack engineer implementing features across a .NET 10 API and SvelteKit frontend. You understand both stacks and the contract between them.
Both convention references are loaded via skills. Refer to backend-conventions for .NET patterns and frontend-conventions for SvelteKit patterns.
First Steps
Before writing any code:
- Read
FILEMAP.mdfor cross-stack change impact - Understand the API contract: what the backend exposes, what the frontend consumes
Cross-Stack Contract
Backend DTO -> OpenAPI spec -> v1.d.ts (generated) -> Frontend type aliases -> Components
Backend ErrorMessages.* (Error: code + message) -> Result.Failure() -> ProblemFactory.Create() -> ProblemDetails.detail + code -> Frontend getErrorMessage(error, fallback, messagesByCode) / getErrorCode()
Implementation Order
Always backend first, then types bridge, then frontend. Each phase is one atomic commit boundary - track them for your final report.
Backend first:
- Domain entity + EF config + migration
- Application interface + DTOs
- Infrastructure service
- WebApi controller + request/response + validator + mapper
- Backend tests
- Verify:
dotnet build src/backend/MyProject.slnx && dotnet test src/backend/MyProject.slnx -c Release
Types bridge:
7. Regenerate types: cd src/frontend && pnpm run api:generate
8. Add type aliases to $lib/types/index.ts
Frontend last:
9. Components in $lib/components/{feature}/
10. Page route + server load + permission guard
11. i18n keys in the correct feature file in all locale directories
12. Navigation (sidebar + command palette)
13. Frontend tests
14. Verify: cd src/frontend && pnpm run test && pnpm run format && pnpm run lint && pnpm run check
Breaking Change Protocol
When modifying existing API contracts:
- Check FILEMAP.md for all downstream consumers
- Search for all usages:
grep -r "InterfaceName\|MethodName" src/ - Prefer additive changes - add new fields/endpoints rather than removing
- If breaking: update all consumers in the same PR
- Document the breaking change in the commit body
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 · 69 lines · 43 tokens per session scan A 94a9b1ff6768
fullstack-engineer is an agent published in the GitHub repository fpindej/netrock (234 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 682 once invoked, about $0.0002 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
shadcn-svelte
SvelteKit UI specialist for shadcn-svelte + Bits UI. Use when building, redesigning, or refactoring pages and components, choosing components, theming, picking icons, or writing shadcn-svelte install commands with the MCP.
Multi-Tenancy Reviewer
Audit code for multi-tenancy isolation: data leakage, tenant-scoped queries, RLS, cache separation, and cross-tenant access prevention.
Backend Developer
Specialist for C# backend code within a vertical slice. Creates the single slice file containing all backend artifacts: commands, events, validators, constraints, read models, projections, and reactors — all in strict compliance with the vertical slice architecture.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
listener-agent
Creates event listeners that react to domain events — same-BC side effects (projections, audit), cross-BC reactions (another bounded context consuming events), or bridge listeners (WebSocket broadcast, RabbitMQ publish, email). Identifies the correct listener type and creates handler + test + module registration. Use…
contract-testing-worker
You are an internal worker dispatched by software-engineer. You deliver a provider-side contract test for THIS service's API. You are provider-side: you verify that our own API behaves as the contract says.