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 perniemann/pnCore --skill pn-devops-automationgit clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/perniemann/pncore/pn-devops-automation)<a href="https://agentmods.dev/skills/perniemann/pncore/pn-devops-automation"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-devops-automation/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/perniemann/pncore/pn-devops-automation"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-devops-automation.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.00036 | $0.00280 |
| Opus 5 | $0.00018 | $0.00140 |
| Sonnet 5 | $0.00007 | $0.00056 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
pn-devops-automation 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
DevOps automation
When to use
- CI/CD pipeline design or improvement.
- Infrastructure as Code (Terraform, CloudFormation).
- Docker, Kubernetes, deployment strategy.
- Monitoring, alerting, zero-downtime deploys.
Workflow
- Assess: Current infra, deployment pain points.
- Design: Pipeline stages, deployment strategy (blue-green, canary).
- Implement: IaC, CI config, monitoring/alerting.
- Verify: Rollback procedure, runbooks.
Output
- Pipeline or IaC changes with stages, deployment strategy, rollback path, and monitoring or alerting hooks described for operators.
Guardrails
- No secrets in VCS; follow pn-backend-philosophy for credentials and pn-config-review for pools, timeouts, and limits.
Integration
- pn-ci-triage, pn-ci-fix — CI pipeline fixes.
- pn-ci-dev-prod-split — Environment separation.
- pn-config-review — Connection pools, timeouts.
- pn-backend-philosophy — Secrets, error handling.
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 · 36 lines · 36 tokens per session scan A bd4ab10c4eac
pn-devops-automation is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 280 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
secrets-management
Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
typescript
TypeScript coding conventions, best practices, and patterns for writing clean, maintainable code.