security-review

Audit Ansible, Docker, and Kubernetes configurations for security vulnerabilities with severity-rated findings.

2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/DanielH2018/server --skill security-review-danielh2018
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/DanielH2018/server/tree/main/.claude/skills/security-review
Command: npx skills add https://github.com/DanielH2018/server --skill security-review-danielh2018

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Infrastructure-as-code repositories accumulate security risks like hardcoded secrets, privileged containers, and missing authentication middleware that are easy to miss during manual review. This Skill systematically audits your homelab codebase against project-specific security standards and produces calibrated, evidence-backed findings. ## Core Features & Use Cases - Secret Exposure Detection: Scans Ansible vars, templates, and inventory files for plaintext credentials, unencrypted SOPS files, and hardcoded passwords in Jinja2 templates. - Configuration Hardening Review: Flags privileged containers, host network modes, overly broad volume mounts, missing TLS, and services bypassing Authelia forward-auth. - False-Positive Filtering: Requires each finding to cite specific file:line evidence, checks git history before flagging, and states exploit preconditions in a Bounds line to keep severity honest. - Use Case: Before deploying changes to a k3s homelab, run a review to catch a new IngressRoute missing the Authelia middleware or a secret accidentally committed to group_vars. ## Quick Start Run a security review of the repository and report any exposed credentials or missing authentication middleware with severity ratings.

Frequently Asked Questions about security-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Ansible playbooks for hardcoded secrets?▼

Scan vars, inventory, and Jinja2 templates for plaintext values where secrets are expected, and verify that sensitive files are SOPS-encrypted. Templates should reference secrets as variables, and tasks handling credentials must set no_log: true.

How to check if Docker containers have insecure configurations?▼

Review compose templates for privileged mode, host network mode, broad volume mounts like /var/run/docker.sock, and unexpected cap_add entries. Each finding should cite the specific file and line, with documented justification required for intentional exceptions.

What severity levels should a security review report use?▼

Use four levels: Critical for immediate credential exposure or compromise risk, High for significant exposure like missing authentication, Medium for increased attack surface, and Low for best-practice gaps. Each finding should state its exploit preconditions to keep ratings calibrated.

How do I avoid false positives in automated security reviews?▼

Disprove each candidate finding before reporting by citing the file:line of the defense that makes it safe, checking all writers and callers of a value, and reviewing git history for prior fixes. Never trust comments or reassuring names without verifying actual code behavior.

Which services can legitimately skip SSO authentication middleware?▼

Services with their own authentication like Jellyfin, unauthenticated health-check endpoints, and non-HTTP protocols like WireGuard or game servers can skip forward-auth. Anything else lacking the middleware should be flagged unless a documented reason exists.