OpenSkillIndex← back to search
claude-code

Forgent infrastructure-config-audit

Production configuration security assessment through policy validation-based skill consuming config_files, infrastructure_code to produce config_audit_report

install
source · Clone the upstream repo
git clone https://github.com/mirandaguillaume/forgent
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/mirandaguillaume/forgent "$T" && mkdir -p ~/.claude/skills && cp -r "$T/internal/bench/fixtures/imported/wshobson/output-standard/skills/infrastructure-config-audit" ~/.claude/skills/mirandaguillaume-forgent-infrastructure-config-audit && rm -rf "$T"
manifest: internal/bench/fixtures/imported/wshobson/output-standard/skills/infrastructure-config-audit/SKILL.md
source content

Infrastructure Config Audit

Guardrails

  • timeout: 300s
  • require_production_config_approval: true
  • validate_before_deployment: true

Context

Consumes: config_files, infrastructure_code Produces: config_audit_report Memory: short-term

Strategy

Approach: Production configuration security assessment through policy validation Tools: read_file, grep, search, bash

Steps

  1. Review production configuration security
  2. Validate container and Kubernetes manifests
  3. Assess Infrastructure as Code templates
  4. Check CI/CD pipeline configurations
  5. Verify secrets management setup
  6. Validate monitoring configurations

Security

  • Filesystem: read-only
  • Network: allowlist