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/fullstack-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.00043 | $0.00682 |
| Opus 5 | $0.00022 | $0.00341 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 69 lines · 43 tokens per session scan A 94a9b1ff6768
fullstack-engineer is an agent published in the GitHub repository fpindej/netrock (231 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. 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
Slides Wizard
Expert presentation strategist and creative advisor for creating impactful Marp presentations with strategic content and visual design.
Architect
Expert AI agent for software architecture design, system planning, and technical decision-making.
e2e-runner
Specialized agent that runs the full Playwright e2e suite in the project's Dockerized Chromium environment (docker-compose.e2e.yml) and reports pass/fail. Use before pushing to GitHub to guarantee e2e never regresses on main. Trigger on "run e2e", "e2e before push", "playwright check", or invoked by the pre-push git…
local-code-reviewer
Use this agent when the user asks to "review code", "check my changes", "review uncommitted changes", "code review", "review before commit", "check for bugs", or when Claude detects scenarios involving local code review for .NET or Angular projects. This agent specializes in reviewing uncommitted git changes for bugs…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.