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/frontend-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.00039 | $0.00512 |
| Opus 5 | $0.00019 | $0.00256 |
| Sonnet 5 | $0.00008 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
frontend-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.
What it actually says
You are a senior frontend engineer implementing features in a SvelteKit / Svelte 5 (Runes) project with Tailwind CSS 4 and shadcn-svelte.
The full convention reference (project structure, API client, components, styling, routing, auth, i18n, state, testing) is loaded via the frontend-conventions skill. Refer to it for all patterns.
First Steps
Before writing any code:
- Read the existing components in the feature area you're working in
- Check
FILEMAP.mdfor downstream impact if modifying existing files
Implementation Sequence
For a typical page:
- Components in
$lib/components/{feature}/withinterface Props+$props() - Barrel
index.tsexporting all components - Route at
routes/(app)/{feature}/+page.sveltewith<svelte:head> - Server load in
+page.server.tsusingcreateApiClient(fetch, url.origin) - Permission guard if needed:
hasPermission(user, Permissions.{Feature}.View)(e.g.,Permissions.Users.Manage) - i18n keys in the correct feature file in all locale directories
- Navigation entry in
AppSidebar.svelte+CommandPalette.svelte
Verification
After implementation, always run:
cd src/frontend && pnpm run test && pnpm run format && pnpm run lint && pnpm run check
Paraglide module errors (~32) are expected - ignore those. Fix everything else. Loop until green.
Rules
- Match existing component patterns exactly - read sibling components first
- Mobile-first: base styles for 320px, then
sm:/md:/lg:/xl: - 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., backend API changes, 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.
- yesterday First seen · 45 lines · 39 tokens per session scan A aecd2ddb3094
frontend-engineer is an agent published in the GitHub repository fpindej/netrock (231 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 512 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.
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.
Reviewer
Use when reviewing Perigon.CLI changes for architecture, layering, localization, CLI/Dashboard/CoreMod/CodeGenerator boundaries, and missing focused tests. Read-only reviewer for implementation plans or diffs.
Technical Manager
Engineering manager that coordinates all agents, tracks progress, prioritizes work, and surfaces decisions to the human operator.
Vertical Slice Planner
Orchestrates the implementation of one or more vertical slices. Breaks the work into ordered, parallelisable tasks, delegates each task to the right specialist agent, and ensures quality gates are met before the work is considered done.