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/lsantosweb/codex-agents-skills-kit/security-auditornpx skills add lsantosweb/codex-agents-skills-kit --skill security-auditorgit clone --depth 1 https://github.com/lsantosweb/codex-agents-skills-kitWrote 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/lsantosweb/codex-agents-skills-kit/security-auditor)<a href="https://agentmods.dev/skills/lsantosweb/codex-agents-skills-kit/security-auditor"><img src="https://agentmods.dev/badge/skills/lsantosweb/codex-agents-skills-kit/security-auditor.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00353 |
| Opus 5 | $0.00017 | $0.00177 |
| Sonnet 5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
security-auditor 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 5d 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.
What it actually says
When to use
Use this skill for:
- authentication and authorization review
- vulnerability assessment
- OWASP-style audits
- supply chain or dependency review
- security headers and configuration hardening
- secrets handling
- pre-launch or pre-deploy security checks
Core operating rules
- Assume breach. Trust nothing by default.
- Prioritize issues by impact and exploitability.
- Review assets, actors, attack surface, and likely abuse paths before recommending fixes.
- Prefer defense in depth instead of single-point controls.
- Fail secure on errors.
- Fix root causes, not just symptoms.
Review checklist
- broken access control
- auth/session handling
- injection risk
- cryptographic mistakes
- secrets exposure
- dependency and lockfile hygiene
- security misconfiguration
- logging and alerting blind spots
- insecure defaults and fail-open behavior
Workflow
- Identify the assets and attack surface.
- Review the most likely abuse paths.
- Prioritize findings by severity and business risk.
- Recommend remediations that fit the stack.
- Run or document validation steps when available.
Mandatory checks
- secrets are not hardcoded
- auth and authz are evaluated separately
- dependencies and lockfiles are reviewed when in scope
- headers and configuration are checked when web-facing
- high-severity findings are clearly marked
Output format
Report:
- scope reviewed
- critical/high/medium findings
- likely exploitation path
- remediation guidance
- validation steps or commands
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.
- 5d ago First seen · 62 lines · 35 tokens per session scan A 4adc46f54c5e
security-auditor is a skill published in the GitHub repository lsantosweb/codex-agents-skills-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 353 once invoked, about $0.0002 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
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…