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 skills/fpindej/netrock/frontend-conventionsnpx skills add fpindej/netrock --skill frontend-conventionsgit 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/skills/fpindej/netrock/frontend-conventions)<a href="https://agentmods.dev/skills/fpindej/netrock/frontend-conventions"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/frontend-conventions.svg" alt="Measured on agentmods" 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.03187 |
| Opus 5 | $0.00014 | $0.01594 |
| Sonnet 5 | $0.00005 | $0.00637 |
| Haiku 4.5 | $0.00003 | $0.00319 |
Grade A, and why
frontend-conventions 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 6d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Conventions (SvelteKit / Svelte 5)
Project Structure
src/
├── lib/
│ ├── api/ # client.ts, error-handling.ts, mutation.ts, backend-monitor.ts, v1.d.ts (GENERATED)
│ ├── auth/ # auth.ts (getUser, logout), middleware.ts (token refresh)
│ ├── components/
│ │ ├── ui/ # shadcn (generated, customizable)
│ │ ├── auth/ # Login/register/reset flows, 2FA step, Turnstile
│ │ ├── layout/ # Header, sidebar, user nav, theme/language toggles
│ │ ├── profile/ # Profile forms, avatar, account details
│ │ ├── settings/ # Password, account deletion, activity log, 2FA management
│ │ ├── admin/ # User/role/job management, audit trail
│ │ ├── dashboard/ # Dashboard widgets
│ │ ├── oauth/ # OAuth provider linking
│ │ └── common/ # Small shared pieces (status indicator, etc.)
│ │ # For the live component inventory, list the barrels: $lib/components/*/index.ts
│ ├── config/ # i18n.ts (client-safe), server.ts (server-only - never export from barrel)
│ ├── state/ # .svelte.ts files only (cooldown, health, shake, theme, sidebar, shortcuts)
│ ├── types/index.ts # Type aliases from API schemas
│ └── utils/ # ui.ts (cn()), permissions.ts, audit.ts, platform.ts, roles.ts, jobs.ts
├── routes/
│ ├── (app)/ # Authenticated (redirect guard)
│ │ └── admin/ # Permission-guarded per page
│ ├── (public)/login/ # Redirect away if logged in
│ └── api/[...path]/ # Catch-all proxy to backend
├── messages/{locale}/*.json # i18n (per-feature: core, auth, admin, etc.)
└── styles/ # themes.css, tailwind.css, animations.css, base.css, utilities.css
API Client
Two layers: lib/api/ (auth-agnostic client factory) and lib/auth/ (all auth concerns).
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.
- 6d ago First seen · 281 lines · 27 tokens per session scan A 04d4244ddff3
frontend-conventions is a skill published in the GitHub repository fpindej/netrock (231 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 3,187 once invoked, about $0.0001 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 skills, from other repositories
api-design
Guidelines for RESTful API design, endpoint naming conventions, and standardizing JSON responses.
python
Enforces FastAPI, Dependency Injection, and general Python coding standards based on the repository structure.
python-testing
Guidelines for Python testing using pytest and pytest-asyncio. Use when writing or debugging backend tests.
react
Guidelines for the React frontend, TanStack ecosystem, and React 19 standards. Use when modifying the UI.
react-testing
Frontend testing standards using Vitest, React Testing Library, and Playwright. Use when writing UI tests.
documentation
Standards for code documentation, docstrings, and maintaining README files.