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/new-featurenpx skills add fpindej/netrock --skill new-featuregit 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-feature)<a href="https://agentmods.dev/skills/fpindej/netrock/new-feature"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/new-feature.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 | $0.00011 | $0.00469 |
| Opus 5 | $0.00005 | $0.00234 |
| Sonnet 5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
new-feature 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 5d 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.
What it actually says
Creates a full-stack feature: backend entity through to frontend page.
Infers everything possible from the feature description. Asks only when genuinely ambiguous (multiple valid designs with different tradeoffs). Prefers conventions from existing features.
Steps
This chains entity -> service/API -> frontend. Commit atomically after each logical unit.
Backend - Entity (see /new-entity):
- Domain: entity + enums + error messages
- Infrastructure: EF config + DbSet + migration
- Verify:
dotnet build src/backend/MyProject.slnx- loop until green - Commit:
feat({feature}): add {Entity} entity and EF configuration
Backend - Service & API (see /new-endpoint):
- Application:
I{Feature}Service+ Input/Output DTOs - Infrastructure:
{Feature}Service(internal) + DI extension - WebApi: controller + request/response DTOs + mapper + validators + Program.cs wiring
- Write tests: component, API integration, validator
- Verify:
dotnet test src/backend/MyProject.slnx -c Release- loop until green - Commit:
feat({feature}): add {Feature} service and API endpoints
Frontend (see /new-page):
- Regenerate types:
cd src/frontend && pnpm run api:generate - Add type alias to
src/frontend/src/lib/types/index.ts - Create components in
$lib/components/{feature}/with barrelindex.ts - Create page in
routes/(app)/{feature}/ - Add i18n keys to the correct feature file in all locale directories
- Add sidebar navigation entry and command palette entry (both with permission if guarded)
- Verify:
cd src/frontend && pnpm run format && pnpm run lint && pnpm run check- loop until green - Commit:
feat({feature}): add {feature} frontend page
Always: If build/check fails, read the error, fix it, re-run. Never stop to report a fixable error.
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.
- 5d ago First seen · 42 lines · 11 tokens per session scan A 7b82d7d7fa56
new-feature is a skill published in the GitHub repository fpindej/netrock (231 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 469 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.
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.
python-testing
Guidelines for Python testing using pytest and pytest-asyncio. Use when writing or debugging backend tests.
database-management
Standards for SQLAlchemy async models, PostgreSQL indexing, UTC datetimes, and Alembic migrations.