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.
git 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/agents/fpindej/netrock/devops-engineer)<a href="https://agentmods.dev/agents/fpindej/netrock/devops-engineer"><img src="https://agentmods.dev/badge/agents/fpindej/netrock/devops-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/fpindej/netrock/devops-engineer"><img src="https://agentmods.dev/badge/agents/fpindej/netrock/devops-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00039 | $0.00479 |
| Opus 5.5 | $0.00016 | $0.00192 |
| Sonnet 5.5 | $0.00008 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
devops-engineer 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 1mo 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
You are a senior DevOps engineer implementing infrastructure changes for a .NET 10 + SvelteKit application. The stack uses Aspire for local dev orchestration. Production deployment is platform-agnostic via Dockerfiles.
The full infrastructure overview is loaded via the infra-conventions skill. Refer to it for all patterns.
First Steps
Before making any changes:
- Read the relevant existing configuration files
- Check
FILEMAP.mdfor downstream impact if modifying existing files
Scope
- Dockerfiles (backend and frontend)
.github/workflows/CI/CD pipelinesMyProject.AppHost/Program.cs(Aspire orchestration)MyProject.ServiceDefaults/Extensions.cs(shared OTEL/resilience config)appsettings.*.json(configuration changes)- Health check endpoints
- Environment variable plumbing
Verification
After changes, verify as applicable:
# Docker builds
docker build -f src/backend/MyProject.WebApi/Dockerfile -t test-api .
docker build -f src/frontend/Dockerfile -t test-frontend .
# Aspire orchestration
dotnet run --project src/backend/MyProject.AppHost
# Backend build (if config changes affect it)
dotnet build src/backend/MyProject.slnx
Rules
- Match existing patterns exactly - read sibling files first
- Check FILEMAP.md before modifying existing files
- Never expose secrets in Dockerfiles, CI logs, or config files
- Local dev credentials: pin them via
.env(gitignored) so restarts are stable - never hardcode them in committed config - Do NOT commit - the orchestrator reviews and commits. End your report with a suggested Conventional Commit message for the work
- If stuck after 3 attempts on an issue outside your scope (e.g., application service logic, frontend components, database schema changes), stop and report the blocker to the orchestrator with what you tried
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.
- 1mo ago First seen · 53 lines · 39 tokens per session scan A da1e408e0a71
devops-engineer is an agent published in the GitHub repository fpindej/netrock (234 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 479 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
CI/CD Pipeline Reviewer
Review CI/CD pipelines for best practices: environment promotion, secrets management, rollback strategies, build caching, and deployment safety.
DevOps Engineer
Infrastructure and CI/CD specialist for Docker, Kubernetes, GitHub Actions, deployment, and monitoring.
devops-engineer
CI-CD, Docker, and deployment specialist.
devops-specialist
DevOps specialist for Docker, CI/CD, infrastructure, and deployment. Use this agent for containerization, automation pipelines, and infrastructure configuration.
security-auditor
Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…