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 skills add HuntsDesk/ve-kit --skill review-securitygit clone --depth 1 https://github.com/HuntsDesk/ve-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/huntsdesk/ve-kit/review-security)<a href="https://agentmods.dev/skills/huntsdesk/ve-kit/review-security"><img src="https://agentmods.dev/badge/skills/huntsdesk/ve-kit/review-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.1 | $0.00065 | $0.02053 |
| Opus 5 | $0.00032 | $0.01026 |
| Sonnet 5 | $0.00013 | $0.00411 |
| Haiku 4.5 | $0.00006 | $0.00205 |
Grade A, and why
review-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 6d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.claude/ Security Review Protocol
Audits security posture of the Claude Code configuration layer. Scope is deliberately narrow: .claude/ files + settings. Does NOT review app code (that's what /security-review is for).
Part of the review-* skill family. Cites ../_shared/review-checklist.md.
Owner: docs-manager (once registered) or general-purpose fallback. Coordinate with code-reviewer for findings that require pattern validation.
When to invoke
- After adding new MCP servers or hooks
- When granting a new agent broad tool permissions
- Periodic audit (quarterly or after any security-relevant incident)
- Before sharing the project with new teammates
- After modifying
settings.json/settings.local.json
Output contract
Board tasks only. Lean summary to main agent.
Step 1 — Secret scanning in .claude/
Grep recursively under .claude/ for high-signal secret patterns:
sk-[a-zA-Z0-9]{20,}— Anthropic/OpenAI style keysAIza[0-9A-Za-z_-]{35}— Google API keysAKIA[0-9A-Z]{16}— AWS access keysghp_[a-zA-Z0-9]{36}— GitHub tokensxox[baprs]-[a-zA-Z0-9-]+— Slack tokens-----BEGIN (RSA )?PRIVATE KEY-----— private keyspostgres://[^:]+:[^@]+@— Postgres connection strings with embedded passwords- Any hardcoded password inside a hook script
Severity: critical if found. Immediately flag and recommend: (1) rotate the secret, (2) move to Secret Manager or env vars, (3) scrub git history if committed.
Scan locations:
.claude/agents/*.md.claude/skills/**/*.md.claude/rules/*.md.claude/hooks/*.sh.claude/settings.json(should reference env vars, never contain secrets).claude/settings.local.json
Step 2 — Permission audit: settings.json / settings.local.json
Read both files. For each, evaluate:
Allow list red flags:
Bash(*)— inherently broad; safe ONLY with a robust deny list (verify)Write(**)— allows writing anywhere; flag high unless intentionalEdit(**)— sameWebFetch(*)— can exfiltrate; low risk on trusted machines but flag for awarenessmcp__*__*— per-server wildcards; verify MCP server isn't high-risk- Tool grants without qualifiers on specific tools (e.g.,
Bashwithout(...)= everything)
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.
- 6d ago First seen · 189 lines · 65 tokens per session scan A e47b39281a73
review-security is a skill published in the GitHub repository HuntsDesk/ve-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 2,053 once invoked, about $0.0003 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
python-debugging
Use this skill when fixing failing Python tests.
repo-scan
Fast orientation for a new codebase.
safe-refactor
Refactor checklist with guardrails.
mle-workflow
Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.