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/csabakovacs/rulesmith/security-reviewernpx skills add CsabaKovacs/rulesmith --skill security-reviewergit clone --depth 1 https://github.com/CsabaKovacs/rulesmithWrote 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/csabakovacs/rulesmith/security-reviewer)<a href="https://agentmods.dev/skills/csabakovacs/rulesmith/security-reviewer"><img src="https://agentmods.dev/badge/skills/csabakovacs/rulesmith/security-reviewer.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.00030 | $0.00555 |
| Opus 5 | $0.00015 | $0.00278 |
| Sonnet 5 | $0.00006 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
security-reviewer scanned grade A with 1 finding 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 4d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Check for injection risks (command injection via child_process, path traversal, template injection). How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review
Reviews changed files for security vulnerabilities and unsafe patterns.
When to Activate
- When changes touch: request/input handling, authentication or authorization, database queries or persistence, file upload or access, HTML rendering or user-generated content, external API calls or webhooks, or secrets/tokens/sensitive data.
- Skip when changes are purely internal logic with no external surface.
Review Methodology
Follow these steps in order:
- Identify security-relevant changes in the diff.
- Check for injection risks (command injection via child_process, path traversal, template injection).
- Verify file system safety: all paths through
resolveRepoRelative+assertPathInsideRepo. (evidence: packages/core/src/fs/safe.ts) - Check write operations restricted to
WRITE_ALLOWLIST. (evidence: packages/core/src/fs/safe.ts) - Verify MCP tool inputs validated via Zod schemas. (evidence: packages/mcp/src/server.ts)
- Check for unsafe
eval, prototype pollution, or unvalidated user input. - Verify symlink rejection in
readFileSafe. (evidence: packages/core/src/fs/safe.ts) - Classify findings as critical (block merge), important (fix before deploy), or minor (track).
- Report ONLY when issues are found — produce no output if the review passes clean.
Stack-Specific Security Rules
- Path traversal: all file paths must use
resolveRepoRelativeguards. (evidence: packages/core/src/fs/safe.ts) - Prototype pollution and unsafe
eval/innerHTMLin template or AST processing. maxBytesPerFilelimits enforced to prevent memory exhaustion. (evidence: packages/core/src/fs/safe.ts)- Artifact store TTL and max size prevent memory leaks. (evidence: packages/core/src/render/index.ts)
Boundaries
- Do NOT apply fixes — security changes require explicit human approval.
- Do NOT flag theoretical risks that cannot be exploited in the current context.
- Focus on the changed code, not pre-existing vulnerabilities (unless the change worsens them).
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.
- 4d ago First seen · 59 lines · 30 tokens per session scan A f8ddb6fa2e25
security-reviewer is a skill published in the GitHub repository CsabaKovacs/rulesmith (15 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 555 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). 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.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…