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 jschulte/claude-plugins --skill health-audit-opsgit clone --depth 1 https://github.com/jschulte/claude-pluginsWrote 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/jschulte/claude-plugins/health-audit-ops)<a href="https://agentmods.dev/skills/jschulte/claude-plugins/health-audit-ops"><img src="https://agentmods.dev/badge/skills/jschulte/claude-plugins/health-audit-ops/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/jschulte/claude-plugins/health-audit-ops"><img src="https://agentmods.dev/badge/skills/jschulte/claude-plugins/health-audit-ops.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.00089 | $0.09039 |
| Opus 5.5 | $0.00036 | $0.03616 |
| Sonnet 5.5 | $0.00018 | $0.01808 |
| Haiku 4.5 | $0.00009 | $0.00904 |
Grade A, and why
health-audit-ops 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 24d 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 — 595 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ops & Deployment Readiness Audit Skill
Use this skill when the user wants a deep audit of a codebase's operational readiness — can this thing be safely deployed, monitored, rolled back, and operated in production? The skill may audit the whole operational layer or focus on a user-specified deploy path, environment, CI workflow, infrastructure slice, secret surface, or observability concern. This is not a code quality audit (health-audit covers that). This is the operational layer: CI/CD pipelines, infrastructure as code, deployment safety, monitoring and observability, secret management, disaster recovery, scaling, and incident response.
Mission
Perform a rigorous, evidence-backed assessment of a repository's operational maturity and deployment readiness. Evaluate everything visible in the repo that affects how the software gets built, shipped, run, monitored, and recovered: CI/CD configs, Dockerfiles, IaC definitions, monitoring configs, deployment scripts, runbooks, and environment setup.
Think like an SRE who just joined the team and needs to understand how this thing runs. Think like an incident commander at 3 AM — what's going to help or hurt?
Do not produce vague "best practices" fluff. Do not invent operational problems. Do not criticize the absence of infrastructure that may exist outside the repository (managed services, external monitoring platforms, vendor-hosted tooling). DO flag when the repo has zero operational concerns addressed — that itself is a significant finding.
Focus Prompt Support
This skill can take an optional prompt that describes the ops area to focus on.
Examples:
- "Focus on the deploy pipeline"
- "Review Kubernetes manifests and rollout safety"
- "Audit secrets handling"
- "Look at monitoring and alert coverage"
- "Review environment parity between staging and production"
When a focus prompt is provided:
- Treat it as the primary audit scope
- Resolve it into concrete pipelines, scripts, IaC, environment configs, runtime manifests, and monitoring artifacts
- Audit out-of-scope areas only when they are required to explain an in-scope operational risk
- Keep findings, scores, and recommendations scoped to that area instead of implying a full operational-readiness grade
- State assumptions, included environments, excluded environments, and unverifiable external tooling plainly
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.
- 24d ago First seen · 595 lines · 89 tokens per session scan A b925099f689d
health-audit-ops is a skill published in the GitHub repository jschulte/claude-plugins (0 stars, last pushed 25d ago), licensed MIT. It adds 89 tokens to every session and 9,039 once invoked, about $0.0004 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-10-12.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
devops-deployment
CI/CD, containers and infrastructure as code: GitHub Actions, Docker, Kubernetes, Helm, Terraform. Use when setting up pipelines or deployments.
CI/CD Pipeline Advanced
Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.
devops-automator
Expert DevOps engineer for CI/CD, IaC, Kubernetes, and deployment automation. Activate on: CI/CD, GitHub Actions, Terraform, Docker, Kubernetes, Helm, ArgoCD, GitOps, deployment pipeline, infrastructure as code, container orchestration. NOT for: application code (use language skills), database schema (use…
checkov
Checkov is an open-source static analysis tool that scans infrastructure-as-code (Terraform, CloudFormation, Kubernetes, Helm, Dockerfile, ARM, Bicep and more) for security misconfigurations and compliance violations. Use it to scan Terraform or Kubernetes manifests before deploy, add a security gate to CI/CD with…