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.
/plugin marketplace add thevibeworks/claude-code-docsnpx agentmods add plugins/thevibeworks/claude-code-docs/claude-securitygit clone --depth 1 https://github.com/thevibeworks/claude-code-docsGrade 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 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.
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.
What it actually says
{
"name": "claude-security",
"version": "0.10.2.3",
"description": "Deep vulnerability scanning of your own code, run entirely inside your Claude Code session at a chosen effort tier, with every finding challenged before it is reported and the verification tally computed in code. Turns surviving findings into targeted patches, each verified by a panel of agents, that you apply when you choose. See the plugin README for the tiers, the report format, and the trust model.",
"author": {
"name": "Anthropic",
"email": "[email protected]"
},
"license": "SEE LICENSE IN LICENSE",
"keywords": [
"security",
"vulnerability",
"scan",
"audit",
"appsec",
"code-review",
"remediation",
"autofix"
]
}
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 · 21 lines scan A 0536c9089d4e
claude-security is a plugin published in the GitHub repository thevibeworks/claude-code-docs (38 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
trigger-tree
See which docs your AI actually discovers — local documentation telemetry for Claude Code.
slideops
Turn a repository into a slide deck, then find out the day it stops matching the code. Ships slideops (repo to deck, with citation-based freshness checking) and slides-to-pdf (any hash-navigated HTML deck to a verified PDF).
record-tutorial
Record screen and generate narrated tutorial videos with AI voice-over.
moxie-docs
Plugin marketplace listing 1 plugin: moxie-docs.
skill-engine
Teach Claude your codebase, then keep it taught. On opt-in, clones registered git sources to a local cache (/.cache/skill-engine/) and installs per-skill context files under your project's .claude/skills/. Reads only paths you register.