Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add thevibeworks/claude-code-docs/plugin install claude-securityWrote 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/thevibeworks/claude-code-docs/claude-security)<a href="https://agentmods.dev/skills/thevibeworks/claude-code-docs/claude-security"><img src="https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/claude-security/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/thevibeworks/claude-code-docs/claude-security"><img src="https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/claude-security.svg" alt="Reviewed on agentmods" width="80" 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.00099 | $0.01376 |
| Opus 5.5 | $0.00040 | $0.00550 |
| Sonnet 5.5 | $0.00020 | $0.00275 |
| Haiku 4.5 | $0.00010 | $0.00138 |
Grade A, and why
claude-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 24d 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.
This is a copy
100% identical to claude-security — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Security
- Session start time (UTC): !
date -u +%Y%m%d-%H%M%S
The front-desk menu
This is the front desk. Its whole purpose is to work out which job the user wants and drive it, following that job's recipe.
-
If the user already asked for a specific job — in the arguments (
$ARGUMENTS) or in plain text ("scan this repo", "scan my branch", "fix the findings", a bare commit sha) — do that job directly and skip the menu. The recipe still asks its own single follow-up question wherever the request left one open. -
Otherwise, open with the menu. Call AskUserQuestion once, single select,
header: "Job",question: "What would you like to do?", offering exactly these three options (never invent others — the tool adds its own free-text entry). The menu is your first user-visible act; no text of any kind comes before it.Offer these three options:
"Scan codebase" is the recommended pick — it carries " (Recommended)" and goes first; the other two keep this order.
-
Then note auto mode once, and Read the chosen job's recipe and follow it. As soon as the job is known — picked on the menu, or named directly in step 1 — first emit exactly one fixed plain-text line, worded identically every time: "Claude Security works best in auto mode. To enable it, press Shift+Tab until the status bar shows auto mode, or restart with
claude --permission-mode auto." It is a note, not a question — say it once, never reword or size it, and do not diagnose the user's settings (whether auto mode is available to them is not yours to determine). Then read the recipe, even when the request leaves nothing to ask — it says how to launch the job and wait for it, so never call Workflow before reading it. Where the request left a question open, the recipe opens with its own one-question sub-menu — which kind of scan, or which patch mode — built from the repository's real state, and every sub-menu has an "I don't know" choice that the recipe resolves to a sensible default itself. So the user answers at most a couple of questions, then one fixed confirmation before a scan actually starts (skipped only when their request already accepted the scan's time or token cost), and the run goes quiet; ask them all now, while the user is present.
What ships with it
6 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.
- 24d ago Changed · +27 tokens per session 58898a55aa8d
- 1mo ago Changed · +1 lines 7e7b345240a3
- 1mo ago First seen · 69 lines · 72 tokens per session scan A 866561e1de52
claude-security is a skill published in the GitHub repository thevibeworks/claude-code-docs (158 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 1,376 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to claude-security, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
requesting-code-review
Guides dispatching a code-reviewer subagent to verify work before proceeding. Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
creating-pull-requests
When to open a pull request in the DorkOS repo (review the pushed branch first, open the PR after it converges), how the automated review behaves (skip-review, review:light/deep, re-review), and how a PR lands through merge-tail and the merge queue, including what to do when it goes red or is ejected. Use when…
make-pr-easy-to-review
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".
security-review
Perform a focused security review of pending git changes to identify high-confidence security vulnerabilities with real exploitation potential. Use this skill when the user asks for a security review, security audit, vulnerability scan, or wants to check pending changes on a branch for security issues before merging.…
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.