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/eaescob/resiliency_skills/securitynpx skills add eaescob/resiliency_skills --skill securitygit clone --depth 1 https://github.com/eaescob/resiliency_skillsWrote 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/eaescob/resiliency_skills/security)<a href="https://agentmods.dev/skills/eaescob/resiliency_skills/security"><img src="https://agentmods.dev/badge/skills/eaescob/resiliency_skills/security.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.00082 | $0.01270 |
| Opus 5 | $0.00041 | $0.00635 |
| Sonnet 5 | $0.00016 | $0.00254 |
| Haiku 4.5 | $0.00008 | $0.00127 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security
Implement secure coding practices and prevent common vulnerabilities.
Security Checklist
Every application should have:
- Dependency audit - No known vulnerabilities in dependencies
- Input validation - All user input validated and sanitized
- Output encoding - Prevent XSS via proper encoding
- Authentication - Secure auth on protected routes
- Authorization - Proper access control checks
- HTTPS - TLS in production
- Security headers - CSP, HSTS, X-Frame-Options, etc.
- Rate limiting - Protect against brute force
- Secrets management - No hardcoded secrets
Workflow
- Audit dependencies - Check for known vulnerabilities
- Review code patterns - Apply secure coding standards
- Add input validation - Validate all user input
- Configure security headers - Set appropriate headers
- Add rate limiting - Protect sensitive endpoints
- Warn about issues - Alert user to any findings
Dependency Auditing
Node.js
# npm audit
npm audit
npm audit fix
# More thorough with better-npm-audit
npx better-npm-audit audit
Go
# govulncheck (official Go vulnerability checker)
go install golang.org/x/vuln/cmd/govulncheck@latest
govulncheck ./...
# nancy (Sonatype)
go list -json -deps ./... | nancy sleuth
If vulnerabilities found: Warn user and suggest fixes. Never silently ignore.
Reference Guides
Dependency Auditing
See references/dependency-audit.md for:
- Automated audit setup (CI/CD)
- Fixing vulnerable dependencies
- Allowlisting known issues
Secure Coding Patterns
See references/secure-coding.md for:
- Input validation patterns
- SQL injection prevention
- XSS prevention
- CSRF protection
API Protection
See references/api-protection.md for:
- Rate limiting implementation
- Security headers configuration
- CORS configuration
- Request validation
What ships with it
3 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.
- 5d ago First seen · 190 lines · 82 tokens per session scan A 66c8aad36458
security is a skill published in the GitHub repository eaescob/resiliency_skills (2 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 82 tokens to every session and 1,270 once invoked, about $0.0004 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…