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.
git clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/plugins/dryvist/claude-code-plugins/content-guards)<a href="https://agentmods.dev/plugins/dryvist/claude-code-plugins/content-guards"><img src="https://agentmods.dev/badge/plugins/dryvist/claude-code-plugins/content-guards/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/plugins/dryvist/claude-code-plugins/content-guards"><img src="https://agentmods.dev/badge/plugins/dryvist/claude-code-plugins/content-guards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
content-guards 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 3d 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.
What it actually says
{
"name": "content-guards",
"version": "6.3.1",
"description": "Combined content validation and guard plugin: token-validator, markdown-validator, readme-validator, webfetch-guard, issue/PR backlog limiter, public-repo leakage guard, and script/wrapper-generation guards",
"author": {
"name": "JacobPEvans"
},
"license": "Apache-2.0",
"keywords": [
"hooks",
"validation",
"content-guards",
"token-limits",
"markdown",
"readme",
"webfetch",
"issue-management",
"backlog-limits",
"code-quality"
],
"skills": [
"./skills/validate-readme",
"./skills/native-first"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 129 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago Changed d58114673b1d
- 4d ago Changed 8953f71b1153
- 23d ago Changed · +1 lines 694d8fbffd33
- 1mo ago Changed 35f56d07674f
- 1mo ago Changed 48ba0e89ac31
- 1mo ago Changed 8d542c7bec4e
- 1mo ago Changed 7fee3065c61d
- 1mo ago First seen · 25 lines scan A 394d0708c767
content-guards is a plugin published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
skills-toolkit
Five commands for GitHub skills in Cowork: load from any repo, save iterated versions, share installed skills, sync updates, and auto-detect pasted URLs.
pr-provenance-stamp
Embeds a reviewer-facing provenance receipt into your PR body when Claude runs gh pr create (or glab mr create). A PostToolUse hook (async, zero added latency) records a per-session ledger: tool calls, agent-authored lines, and every test/typecheck command with its real exit code; a PreToolUse (Bash) hook then rewr.
local-ai
From nothing to a working AI setup you own. Scans the machine for models that fit, installs and wires up the right app with consent at every download, shares it over a private URL, and rents a cloud GPU when a model is too big. Needs shell access.
macos-permissions
Audit and control what software on a Mac can see, drive and outlive a reboot. TCC privacy grants across all 40 services and all three permission stores (system, user, and the Sequoia screen-capture plist tccutil cannot reach), including grants stranded by uninstalled apps that macOS never garbage-collects. Plus full p.
rust-tools
SOTA Rust tooling - refactoring, profiling, benchmarking, testing, SIMD, dependency audit.
rad-chrome-extension
MV3 Chrome extension development standards (WXT, React, TypeScript) with two pure-stdlib Python validators that catch what LLM eyeballing misses. Skills cover architecture, MV3 security (CSP, remote code ban, content script isolation), permission minimization and CWS compliance, typed messaging, storage selection…