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 infra-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/infra-conventions)<a href="https://agentmods.dev/skills/fpindej/netrock/infra-conventions"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/infra-conventions.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00020 | $0.00689 |
| Opus 5 | $0.00010 | $0.00345 |
| Sonnet 5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
infra-conventions scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] Health probe binary used in Docker (not curl/wget which add attack surface) How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure Conventions
Overview
Local dev: Aspire AppHost -> PostgreSQL, MinIO, MailPit (containers) + API + Frontend (processes)
Production: User's choice - Docker Compose, Coolify, Railway, Kubernetes, etc.
- Backend Dockerfile: Multi-stage .NET build at
src/backend/MyProject.WebApi/Dockerfile - Frontend Dockerfile: Multi-stage Node/SvelteKit build at
src/frontend/Dockerfile - Production config:
appsettings.jsondefines the full config structure;docs/before-you-ship.mdlists what to configure
Deployment Checklist
Dockerfile Integrity
- All
.csprojfiles referenced by WebApi have COPY lines in the restore layer - Multi-stage build: restore -> build -> publish -> final (no SDK in final image)
-
StripDevConfigremovesappsettings.Development.jsonandappsettings.Testing.json - Health probe binary published separately and copied to final image
- Non-root user (
$APP_UID) in final stage - No secrets baked into image (build args, env vars at build time)
-
.dockerignoreexcludes unnecessary files (bin, obj, node_modules, .git)
Environment Variables
- All configurable options have sensible defaults in
appsettings.json - Sensitive values use placeholders in base config (not real secrets)
- Connection strings use env var substitution, not hardcoded values
-
ASPNETCORE_ENVIRONMENTset toProduction
Aspire (Local Dev)
- AppHost references all infrastructure dependencies
- Port allocation follows the project convention (base+N pattern)
- Credentials pinned via parameters (not randomly generated)
-
WithDataVolume()on stateful resources for persistence across restarts - ServiceDefaults wired: OTEL, service discovery, resilience
- Graceful degradation when not running under Aspire
Health Checks
- API:
/health/live(liveness) and/health/ready(readiness) - Health probe binary used in Docker (not curl/wget which add attack surface)
- Frontend: HTTP check on port 3000
- Start periods appropriate for cold starts (API: 60s, DB: 15s)
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.
- 8d ago First seen · 62 lines · 20 tokens per session scan A b79d9de6c945
infra-conventions is a skill published in the GitHub repository fpindej/netrock (232 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 689 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
ecspresso
ECS deployment tool - deploy, manage, and troubleshoot ECS services.
k8s-dev-deploy
Build, push, and deploy Kurtosis dev images to a Kubernetes cluster without creating a release. Rebuilds engine, core, and files-artifacts-expander as multi-arch Docker images with a unique tag, pushes to the logged-in user's Docker Hub, and restarts the engine. Use when testing local code changes on a k8s cluster.
isrvd-ops
Operations instructions for using the isrvd API to deploy containers, manage services and images, configure routes, handle files, and use a web terminal. The instructions include Python, Node.js, and Bash helper scripts.
coolify
Use when self-hosting apps and databases with Coolify on a VPS you own — install, first-admin lockdown, Git-to-deploy (Nixpacks/Dockerfile/compose), managed Postgres/Redis, scheduled S3 backups, domains + auto-SSL. NOT a PaaS someone else runs (that is railway), NOT sizing/hardening the box (that is hetzner), NOT…
kubernetes
· Write/review Kubernetes manifests, Helm, Kustomize, Gateway API, ArgoCD, sealed secrets. Triggers: 'kubernetes', 'k8s', 'helm', 'kubectl', 'kubernetes deployment', 'pod', 'ingress', 'gateway api'.
staging-deploy
Build, push, migrate, and deploy to staging environment with health check verification. Use when deploying a completed phase to staging.