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/security-conventionsnpx skills add fpindej/netrock --skill security-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/security-conventions)<a href="https://agentmods.dev/skills/fpindej/netrock/security-conventions"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/security-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 | $0.00019 | $0.00871 |
| Opus 5 | $0.00010 | $0.00436 |
| Sonnet 5 | $0.00004 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
security-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 4d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Conventions
Architecture Context
- JWT access tokens in HttpOnly cookies, refresh token rotation
- Permission-based authorization via
[RequirePermission]attributes - Role hierarchy: Superuser > Admin > User > Custom
- PII masking server-side via
PiiMasker/WithMaskedPii- requiresusers.view_piipermission - CSRF protection via Origin header validation on mutations
- CSP with nonce-based script-src
- API proxy in SvelteKit forwards cookies + headers
Security Checklist
Authentication & Authorization
- Auth middleware cannot be bypassed (no unprotected routes that should be protected)
-
[RequirePermission]on every action that needs it - not just[Authorize] - Role hierarchy enforced - cannot manage users at/above your rank
- Cannot modify your own roles, lock yourself, or delete yourself
- Refresh token rotation works correctly - old tokens invalidated
- Permission changes invalidate affected users' tokens and cache
Input Validation
- All input validated on backend (FluentValidation) - frontend validation is UX only
- File uploads: size limits, MIME type validation, no path traversal
- URL fields: restrict to http/https schemes via
Uri.TryCreate - SQL injection: parameterized queries only (EF Core handles this, but check raw SQL)
- No string interpolation in LINQ/SQL queries
- Rate limiting on auth endpoints and mutations
PII Compliance
- Emails, phone numbers, usernames never exposed without
users.view_piipermission - PII masking happens server-side - never rely on frontend
- No PII in logs (structured logging with masking)
- No PII in URLs, tokens, or error messages
- Self-view exemption: users see their own unmasked data
- Audit trail for PII access
Information Leakage
- Error messages use
ErrorMessages.*constants - no stack traces, no internal details -
ProblemDetailsfor all error responses - no anonymous objects - Identity errors: log
.Descriptionserver-side, return static message to client - No sensitive data in JWT claims beyond what's needed
-
SetDbStatementForTextnever set totruein OTEL (captures SQL with PII) -
appsettings.Development.jsonandappsettings.Testing.jsonexcluded from publish
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.
- 4d ago First seen · 80 lines · 19 tokens per session scan A ace2755ca768
security-conventions is a skill published in the GitHub repository fpindej/netrock (231 stars, last pushed 5d ago), licensed MIT. It adds 19 tokens to every session and 871 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.