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/dmoskov/sharedskills/security-auditnpx skills add dmoskov/sharedskills --skill security-auditgit clone --depth 1 https://github.com/dmoskov/sharedskillsWhat 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.00025 | $0.00612 |
| Opus 5 | $0.00013 | $0.00306 |
| Sonnet 5 | $0.00005 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
security-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 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit Skill
Run a comprehensive, language-agnostic security audit on any codebase. Checks for SQL injection, hardcoded secrets, CORS misconfigurations, path traversal, SSRF, auth bypass, race conditions, command injection, and other OWASP Top 10 vulnerability classes.
When to Use
- Before shipping a release or merging a large feature branch
- During periodic security reviews
- When onboarding a new codebase or dependency
- After a security incident to check for similar patterns
- When a task explicitly calls for security hardening
Input
The user provides one of:
- A directory or repository to audit (defaults to current working directory)
- A specific file or module path to focus on
- A vulnerability class to prioritize (e.g., "focus on injection vulnerabilities")
Workflow
Follow prompts/audit-prompt.md for the full audit algorithm.
Quick summary:
- Discover - Identify languages, frameworks, and entry points in the codebase
- Scan - Search for vulnerability patterns across all source files
- Analyze - Read flagged code in context to confirm or dismiss each finding
- Classify - Assign severity (CRITICAL / HIGH / MEDIUM / LOW / INFO) per finding
- Report - Output structured findings with file, line, issue, and fix
Output Format
Each confirmed finding is reported as:
### [SEVERITY] Issue Title
- **File:** path/to/file.ext
- **Line:** 42
- **Category:** SQL Injection | Hardcoded Secret | SSRF | etc.
- **Issue:** Description of the vulnerability and its impact
- **Code:**
vulnerable code snippet
- **Fix:** Specific remediation with corrected code example
A summary table is provided at the end:
| # | Severity | Category | File | Line | Issue |
|---|---|---|---|---|---|
| 1 | CRITICAL | SQL Injection | src/db.py | 42 | User input in raw query |
| ... | ... | ... | ... | ... | ... |
Constraints
- Only report confirmed vulnerabilities with evidence (file path + code)
- Do NOT report style issues, linting warnings, or non-security concerns
- False positives waste reviewer time — when uncertain, note confidence level
- Findings must be actionable: every issue must include a concrete fix
What ships with it
2 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.
- 2d ago First seen · 82 lines · 25 tokens per session scan A dc77e250b71b
security-audit is a skill published in the GitHub repository dmoskov/sharedskills (2 stars, last pushed 11d ago), licensed MIT. It adds 25 tokens to every session and 612 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.