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 skills add fpindej/netrock --skill new-pagegit 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/new-page)<a href="https://agentmods.dev/skills/fpindej/netrock/new-page"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/new-page.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.00013 | $0.00539 |
| Opus 5 | $0.00006 | $0.00269 |
| Sonnet 5 | $0.00003 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
new-page 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 7d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creates a new frontend page with routing, i18n, and navigation.
Infers route, route group, components needed, and data requirements from context. Defaults to (app) (authenticated). Asks only if genuinely ambiguous.
Templates
Use these as starting points - fill in the specifics from context:
Conventions
- Button layout: All action/submit buttons use
w-full sm:w-autowith wrapperflex flex-col gap-2 sm:flex-row sm:justify-end. Default size only (nosize="sm"orsize="lg").
Steps
Components (if needed):
- Create feature folder:
src/frontend/src/lib/components/{feature}/ - Create components with
interface Props+$props() - Create barrel
index.tsexporting all components
Page:
- Create route directory:
src/frontend/src/routes/(app)/{feature}/- Or
(public)/{feature}/for unauthenticated pages
- Or
- Create
+page.sveltewith<svelte:head>using i18n title - If server data needed: create
+page.server.tsusingcreateApiClient(fetch, url.origin) - If admin page: add entry to
adminRoutesin$lib/config/routes.tswith path and permission - If permission-guarded: add check in
+page.server.ts:if (!hasPermission(user, adminRoutes.feature.permission)) throw redirect(303, routes.dashboard);
Integration:
- Add i18n keys to the correct feature file in all locale directories
- Add navigation entry in
AppSidebar.svelte(usingadminRoutes.feature.pathand.permissionfor admin pages) - Add matching entry in
CommandPalette.svelte(usingadminRoutes.feature.pathand.permissionfor admin pages) - If public page: add route to
publicRoutesinsrc/frontend/src/routes/sitemap.xml/+server.ts
Verify and commit:
cd src/frontend && pnpm run format && pnpm run lint && pnpm run check- fix errors, loop until green- Commit:
feat({feature}): add {feature} page
Paraglide module errors (~32) are expected at check time - ignore those. Fix everything else.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 52 lines · 13 tokens per session scan A f087eb0888bb
new-page is a skill published in the GitHub repository fpindej/netrock (231 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 539 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
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.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
typescript-craftsmanship
Professional TypeScript + React + Next.js coding standards enforcer. Use this skill whenever writing, reviewing, or refactoring TypeScript code in any project — whether it's a new feature, a bug fix, a refactoring pass, or a code review. Trigger on: any TypeScript or TSX file creation/editing, "clean up this code"…
debug-triage
· Triage a live incident to localize an unknown failing layer, then route. Triggers: incident, outage, triage, production down, crashloop, 502. Not for known-component debugging (systematic-debugging) or repo audits (deep-audit).
astro-docs
Comprehensive Astro framework reference covering components, pages, layouts, routing, styling, markdown, content collections, islands architecture, server islands, actions, middleware, endpoints, data fetching, view transitions, integrations, deployment, environment variables, imports, images, fonts, i18n, sessions…