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 agentmods add skills/evilfreelancer/secs/iac-securitynpx skills add EvilFreelancer/secs --skill iac-securitygit clone --depth 1 https://github.com/EvilFreelancer/secsWhat 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 | $0.00105 | $0.02525 |
| Opus 5 | $0.00053 | $0.01262 |
| Sonnet 5 | $0.00021 | $0.00505 |
| Haiku 4.5 | $0.00011 | $0.00252 |
Grade A, and why
iac-security 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 2d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure as Code Security
Thin router for IaC static analysis. Pick the right workflow, run scanners in parallel, aggregate findings into schemas/finding.json, and (where org controls demand it) author Rego policies via the policy-as-code loop. Detailed per-stack commands and rule references live under references/; multi-step runbooks live under workflows/.
When to Use
- Scan Terraform
.tf/ plan JSON for misconfigurations - Audit CloudFormation YAML/JSON templates
- Validate Kubernetes manifests (incl. rendered Helm / kustomize)
- Validate Helm charts pre- and post-render
- Scan ARM / Bicep templates for Azure misconfigurations
- Verify CIS benchmark compliance across AWS / Azure / GCP / K8s
- Integrate IaC scanning into PR gates or pre-commit hooks
- Author custom OPA/Rego policies for org-specific controls
Trigger Phrases
- "scan this Terraform / audit my CloudFormation / check Kubernetes manifests"
- "validate Helm chart security" · "IaC security scan" · "infrastructure compliance"
- "write a Rego policy for X" · "add Conftest rule for Y"
When NOT to Use This Skill
- Runtime cloud assessment (live AWS/Azure/GCP accounts, IAM policies in force, runtime resource state) → use
exploiting-cloud-platforms. - Container image CVE scanning, admission control at runtime, cluster live scans → use
container-security. - Secrets discovery in a codebase → use
auditing-supply-chain(pair with this skill for IaC files that contain secrets). - Application source-code SAST → use
auditing-code-for-vulnerabilities/sast. - Pure drift detection vs deployed state — not in scope; use Terraform Cloud / Driftctl / AWS Config.
Decision Tree
What file(s)?
├── .tf / .tf.json / tfplan.json → workflows/terraform_scan.md
├── CFN .yaml/.json/.template → workflows/cloudformation_scan.md
├── K8s manifests (Deployment/etc) → workflows/kubernetes_manifest_scan.md
├── Helm chart (Chart.yaml) → references/helm.md (render → K8s workflow)
├── ARM / .bicep → references/arm_bicep.md
└── Need a custom org rule? → workflows/policy_as_code_loop.md
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/opa_rego_templates.md 5.7 KB
- examples/vulnerable_terraform.tf 3.6 KB
- references/arm_bicep.md 2.6 KB
- references/bounty_patterns_2024_2026.md 8.0 KB
- references/ci_cd_integration.md 3.0 KB
- references/cloudformation.md 2.7 KB
- references/helm.md 2.5 KB
- references/kubernetes_manifests.md 3.0 KB
- references/severity_mapping.md 3.6 KB
- references/terraform.md 4.7 KB
- schemas/finding.json 2.6 KB
- workflows/cloudformation_scan.md 2.3 KB
- workflows/kubernetes_manifest_scan.md 2.8 KB
- workflows/policy_as_code_loop.md 4.8 KB
- workflows/terraform_scan.md 2.9 KB
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.
- 2d ago First seen · 159 lines · 105 tokens per session scan A 5c3072b17ac1
iac-security is a skill published in the GitHub repository EvilFreelancer/secs (10 stars, last pushed 24d ago), licensed Apache-2.0. It adds 105 tokens to every session and 2,525 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
Blue Team Defense & Hardening
System hardening, detection engineering, security baseline monitoring, patch management, defense-in-depth architecture, and security posture improvement.
analyzing-email-headers-for-phishing-investigation
Parse and analyze email headers to trace the origin of phishing emails, verify sender authenticity, and identify spoofing through SPF, DKIM, and DMARC validation.
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware using Ghidra with specialized scripts for function recovery, string extraction, and type reconstruction in stripped Go binaries.
analyzing-prefetch-files-for-execution-history
Parse Windows Prefetch files to determine program execution history including run counts, timestamps, and referenced files for forensic investigation.
analyzing-ios-app-security-with-objection
Performs runtime mobile security exploration of iOS applications using Objection, a Frida-powered toolkit that enables security testers to interact with app internals without jailbreaking. Use when assessing iOS app security posture, bypassing client-side protections, dumping keychain items, inspecting filesystem…
add-tool
Use when adding a new cybersecurity tool to this installer. Walks through editing the right module file, adding to toolsconfig.json, running validators, and syncing MCP server data if needed. Triggers on phrases like "add tool", "add ", "register a new tool", "include X in the installer".