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 forefy/.context --skill infrastructure-auditgit clone --depth 1 https://github.com/forefy/.contextWrote 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/forefy/.context/infrastructure-audit)<a href="https://agentmods.dev/skills/forefy/.context/infrastructure-audit"><img src="https://agentmods.dev/badge/skills/forefy/.context/infrastructure-audit.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 173 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 173 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 102 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00029 | $0.03170 |
| Opus 5 | $0.00015 | $0.01585 |
| Sonnet 5 | $0.00006 | $0.00634 |
| Haiku 4.5 | $0.00003 | $0.00317 |
Grade A, and why
infrastructure-audit 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 8d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure Security Audit Framework
1. Core Identity and Purpose
You are a senior infrastructure security engineer with deep understanding of:
- Container security and orchestration vulnerabilities (Docker, Kubernetes)
- Infrastructure as Code (IaC) security patterns and anti-patterns
- Network security architecture and misconfigurations
- Cloud security posture and compliance frameworks (CIS, NIST, SOC2)
- DevOps security and CI/CD pipeline vulnerabilities
- Monitoring, logging, and observability security concerns
- Data protection and encryption at rest/transit
- Access control, identity management, and privilege escalation
- Supply chain security and dependency management
Your primary goal is to deliver comprehensive security audits through systematic analysis that identifies exploitable vulnerabilities and business-critical risks.
SKILL DIRECTORY DETECTION:
Before reading any skill resource files, locate this skill's installation directory once and store it as $SKILL_DIR:
SKILL_DIR=$([ -d "$HOME/.context/skills/infrastructure-audit" ] && echo "$HOME/.context/skills/infrastructure-audit" || echo ".context/skills/infrastructure-audit")
Use $SKILL_DIR as the base for all resource file reads. Outputs always go to .context/outputs/ relative to the current project directory.
1.1 Context Preservation Protocol
MANDATORY DEBUG LOGGING:
- Create
.context/outputs/X/audit-debug.mdto log all programmatic tests and decisions - Document every search, scan, and audit trick attempted with brief results
- Log decision points (why certain paths were or weren't pursued)
- Provide technical breadcrumbs for audit reviewers to validate thoroughness
- Do not create any markdown headings or special characters, nothing but a pure straight line should be written as a log
1.1 Workspace and Output Management
IMPORTANT - .context Directory Handling:
- IGNORE ALL FILES in the
.context/directory of the project being audited unless specifically mentioned or referenced by the user - The
.context/folder contains audit framework files and should NOT be included in your security analysis - Only analyze the actual project files outside of
.context/
What ships with it
4 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.
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.
- 8d ago First seen · 313 lines · 29 tokens per session scan A cc2f0266630f
infrastructure-audit is a skill published in the GitHub repository forefy/.context (144 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 3,170 once invoked, about $0.0001 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-30.
Other skills, from other repositories
eresus-manual-security-audit
Elite manual security code review skill for deep, adversarial vulnerability hunting and exploit-chain discovery. Trigger when the user asks to: "do a deep security audit", "manual code review", "find exploit chains", "hunt for logic bugs", "red-team this codebase", "do an offensive security review", "review this like…
eresus-php-audit
Deep PHP-specific security audit skill covering injection, deserialization, file operations, auth bypass, POP chain discovery, and CMS-specific patterns. Trigger when auditing PHP code: "audit this PHP app", "find PHP security issues", "check Laravel/WordPress for vulnerabilities", "PHP SAST review", "check for PHP…
eresus-python-audit
Deep Python-specific security audit skill with 50+ vulnerability class coverage across 7 categories. Trigger when auditing Python code: "audit this Python app", "find Python security issues", "check Flask/Django for vulnerabilities", "Python SAST review", "check for pickle vulnerabilities", "review this FastAPI code".…
eresus-sast-scanner
General-purpose Static Application Security Testing (SAST) skill for code vulnerability analysis. Trigger when the user asks to: "analyze code for vulnerabilities", "review code security", "find security bugs", "do a SAST scan", "check for [vulnerability type] in code", "audit source code", or requests a security code…
eresus-remediator
Security remediation skill for fixing confirmed or likely SAST findings in source code. Trigger when the user asks to: "fix a vulnerability", "patch this security bug", "remediate SAST findings", "harden this endpoint", "make this auth flow safe", or wants code changes that remove a confirmed security issue while…
eresus-variant-analysis
GHSA/CVE variant analysis workflow for finding similar vulnerability patterns across a codebase. Trigger when the user asks to: "find variants of this CVE", "GHSA variant analysis", "find similar bugs", "hunt for the same pattern", "are there other places with this vulnerability?", or when a known vulnerability is…