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 batu-sonmez/infraclaude --skill security-reviewgit clone --depth 1 https://github.com/batu-sonmez/infraclaudeWrote 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/batu-sonmez/infraclaude/security-review)<a href="https://agentmods.dev/skills/batu-sonmez/infraclaude/security-review"><img src="https://agentmods.dev/badge/skills/batu-sonmez/infraclaude/security-review/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/batu-sonmez/infraclaude/security-review"><img src="https://agentmods.dev/badge/skills/batu-sonmez/infraclaude/security-review.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.00000 | $0.00515 |
| Opus 5 | $0.00000 | $0.00258 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
security-review 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 11d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure Security Review Checklist
Comprehensive security audit checklist using InfraClaude tools.
Kubernetes Security
Pod Security
- No pods running as root (
security_k8s_audit) - No privileged containers
- Read-only root filesystem where possible
- Resource limits set on all containers
- No host network/PID/IPC namespace sharing
- Security contexts defined for all pods
RBAC
- No overly permissive ClusterRoleBindings
- Service accounts follow least privilege
- No use of default service account for workloads
- Regular review of who has cluster-admin
Network Security
- NetworkPolicies defined for all namespaces
- Default deny ingress/egress policies
- Services not unnecessarily exposed externally
- TLS enabled for all external endpoints
Secrets Management
- Secrets not stored in ConfigMaps
- Secrets not in environment variables (prefer volume mounts)
- External secrets manager integration
- Regular secret rotation
Container Security
Image Security
- Scan images with
security_trivy_scanfor CVEs - No CRITICAL/HIGH vulnerabilities in production images
- Use specific image tags, not
:latest - Images from trusted registries only
- Multi-stage builds to minimize image size
Secret Detection
- Run
security_gitleaks_scanon the codebase - No API keys, passwords, or tokens in code
-
.gitignorecovers sensitive files - Pre-commit hooks for secret detection
Infrastructure Security
Terraform
- State files encrypted and access-controlled
- No hardcoded secrets in HCL files
- Use
terraform_validatebefore applying - Review
terraform_planoutput carefully
Monitoring
- Alerts configured for security events
- Audit logging enabled
- Log aggregation and retention policies
- Anomaly detection for unusual patterns
Remediation Priority
| Severity | SLA | Examples |
|---|---|---|
| Critical | 24h | Privileged containers, exposed secrets, no auth |
| High | 1 week | Running as root, missing network policies |
| Medium | 1 month | Missing resource limits, no image scanning |
| Low | Next quarter | Best practice improvements |
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.
- 11d ago First seen · 70 lines · 0 tokens per session scan A 3d19adb3c256
security-review is a skill published in the GitHub repository batu-sonmez/infraclaude (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 515 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…