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/groupzer0/vs-code-agents/security-patternsnpx skills add groupzer0/vs-code-agents --skill security-patternsgit clone --depth 1 https://github.com/groupzer0/vs-code-agentsWhat 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.00040 | $0.01278 |
| Opus 5 | $0.00020 | $0.00639 |
| Sonnet 5 | $0.00008 | $0.00256 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
security-patterns 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Patterns
Systematic approach to identifying and remediating security vulnerabilities. Use this skill when:
- Reviewing code for security vulnerabilities
- Conducting security audits
- Implementing authentication, authorization, or data handling
- Assessing third-party dependencies
OWASP Top 10 (2021) Quick Detection
A01: Broken Access Control
Detection patterns:
- Missing authorization checks on endpoints
- Direct object references without ownership validation
- Path traversal:
../in file paths - CORS with
Access-Control-Allow-Origin: * - JWT without signature verification
Remediation:
- Implement RBAC/ABAC at controller/service layer
- Validate ownership on every resource access
- Use allowlists for file paths
- Configure CORS with specific origins
A02: Cryptographic Failures
Detection patterns:
- MD5/SHA1 for passwords
- Hardcoded encryption keys
- HTTP for sensitive data
- Weak random:
Math.random(),rand() - Missing encryption at rest
Remediation:
- Use bcrypt/argon2 for passwords (cost ≥12)
- External key management (KMS, Vault)
- TLS 1.2+ everywhere
- Cryptographic RNG only
A03: Injection
Detection patterns:
- String concatenation in SQL/NoSQL queries
- Template literals in HTML without escaping
eval(),exec(),Function()with user input- Shell commands with string interpolation
- LDAP/XPath queries with user input
Remediation:
- Parameterized queries always
- Context-aware output encoding
- Never eval untrusted input
- Use ORM/query builders
A04: Insecure Design
Detection patterns:
- Business logic without rate limiting
- Missing account lockout
- No CAPTCHA on authentication
- Unbounded resource allocation
- Missing threat model documentation
Remediation:
- Rate limit all sensitive operations
- Implement progressive delays
- Bound all allocations
- Document trust boundaries
A05: Security Misconfiguration
Detection patterns:
- Default credentials in config
- Verbose error messages to users
- Debug mode in production
- Unnecessary services enabled
- Missing security headers
What ships with it
9 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.
- references/go-vulnerabilities.md 2.5 KB
- references/java-vulnerabilities.md 2.8 KB
- references/javascript-vulnerabilities.md 2.2 KB
- references/python-vulnerabilities.md 2.2 KB
- references/security-methodology.md 7.1 KB
- references/security-templates.md 3.6 KB
- scripts/check-dependencies.sh 1.9 KB runs code
- scripts/check-secrets.sh 1.9 KB runs code
- scripts/security-scan.sh 3.2 KB runs code
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 · 193 lines · 40 tokens per session scan A bc45b1276f7f
security-patterns is a skill published in the GitHub repository groupzer0/vs-code-agents (284 stars, last pushed 7mo ago), licensed MIT. It adds 40 tokens to every session and 1,278 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…