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 doancan/mags --skill infrastructuregit clone --depth 1 https://github.com/doancan/magsWrote 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/doancan/mags/infrastructure)<a href="https://agentmods.dev/skills/doancan/mags/infrastructure"><img src="https://agentmods.dev/badge/skills/doancan/mags/infrastructure/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/skills/doancan/mags/infrastructure"><img src="https://agentmods.dev/badge/skills/doancan/mags/infrastructure.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.00056 | $0.02691 |
| Opus 5.5 | $0.00022 | $0.01076 |
| Sonnet 5.5 | $0.00011 | $0.00538 |
| Haiku 4.5 | $0.00006 | $0.00269 |
Grade A, and why
infrastructure 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure
Deployment Checklist
Complete every item before deploying to production:
- Environment parity: Verify that staging mirrors production in configuration, dependency versions, and infrastructure topology. Test the exact artifact (container image, binary) that will be deployed to production.
- Health checks: Ensure every service exposes a health endpoint (
/healthor/healthz) that checks database connectivity, cache availability, and critical dependency status. Configure the orchestrator (Kubernetes, ECS) to use this endpoint for readiness and liveness probes. - Graceful shutdown: Handle SIGTERM signals properly. Stop accepting new requests, finish in-flight requests (with a timeout of 30 seconds), close database connections, and flush logs before exiting.
- Rollback plan: Document the exact rollback procedure before deploying. For container deployments, keep the previous image tag available. For database changes, have a tested rollback migration. Verify the rollback procedure works in staging first.
- Database migrations: Run migrations before deploying new application code. Ensure migrations are backward-compatible with the currently running version (see Database Migrations section). Never run destructive migrations during deployment.
- Feature flags: Gate new features behind feature flags for critical releases. This allows disabling a feature without a full rollback. Use a feature flag service (LaunchDarkly, Unleash, or a simple config-based system).
- DNS and SSL: Verify DNS records point to the correct endpoints. Check SSL certificate expiration dates (must be more than 30 days out). Confirm TLS 1.2+ is enforced and older protocols are disabled.
- Smoke tests: Run automated smoke tests immediately after deployment. Test critical user paths: authentication, core business operations, and external integrations. Automate these in the CI/CD pipeline as a post-deploy step.
- Monitoring and alerting: Confirm that dashboards are updated for the new version. Verify alert thresholds are set for error rate spikes, latency increases, and resource exhaustion. Assign an on-call engineer for the deployment window.
- Communication: Notify the team before and after deployment. For user-facing changes, update status pages and changelogs.
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 · 142 lines · 56 tokens per session scan A 9645462e0a69
infrastructure is a skill published in the GitHub repository doancan/mags (3 stars, last pushed 8mo ago), licensed MIT. It adds 56 tokens to every session and 2,691 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-31.
Other skills, from other repositories
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
supply-chain
Secure the software supply chain from source to running container. Covers Cosign keyless image signing (Sigstore/Rekor), SBOM generation and attestation (Syft), vulnerability scanning with severity gates (Trivy/Grype), SLSA Level 2 provenance, and Kyverno/OPA admission enforcement. All open-source, no license cost.…
trivy
Scan container images, filesystems, git repos, and existing SBOMs for CVEs, secrets, and license violations using Trivy. Covers local CLI, CI severity gates with SARIF upload, and continuous monitoring via Trivy Operator (Flux HelmRelease). Use when asked to "scan my image", "check for CVEs", "scan this repo for…
relay-deploy
Set up a complete deployment configuration — Dockerfile, deployment manifest, environment config, and rollback procedure. Use when asked about "deployment setup", "how do I deploy this", "deployment strategy", or "rollback plan".
relay-docker
Build production-ready Dockerfiles with multi-stage builds, security hardening, and docker-compose for local dev. Use when asked to "create Dockerfile", "optimize container", or "dockerize this".
platform-skills
Use when troubleshooting, implementing, reviewing, or auditing platform infrastructure as a system — where Kubernetes, GitOps, CI/CD, and security concerns intersect. Provides structured diagnosis with blast radius, validation steps, and rollback plan for: Kubernetes, Flux CD, Argo CD, Terraform, GitHub Actions…