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/Yashvendra/claude-security-skillsWrote 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/yashvendra/claude-security-skills/audit-context-building)<a href="https://agentmods.dev/plugins/yashvendra/claude-security-skills/audit-context-building"><img src="https://agentmods.dev/badge/plugins/yashvendra/claude-security-skills/audit-context-building.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
audit-context-building 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.
What it actually says
{
"name": "audit-context-building",
"version": "1.1.0",
"description": "Build deep architectural context through ultra-granular code analysis before vulnerability hunting",
"author": {
"name": "Omar Inuwa",
"email": "[email protected]",
"url": "https://github.com/trailofbits"
}
}
What it installs
The manifest is a name and a version. 1 skill, 1 command, 1 agent travel with it, and installing the plugin installs all of them — 80 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.
- 6d ago First seen · 11 lines scan A 2764f01176f9
audit-context-building is a plugin published in the GitHub repository Yashvendra/claude-security-skills (2 stars, last pushed 5mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
rampstack marketplace
RampStack Claude Skills: the website lifecycle as installable skills.
vibing-nvim
Neovim MCP tools, skills, and subagents for vibing.nvim — lets Claude Code read/edit buffers, drive LSP, and manage windows in a running Neovim instance.
hydra
Git Worktree management for parallel agent execution - isolated working directories without Git conflicts.
skill-bus
The skill for connecting skills. Connect context, conditions, and other skills to any skill — no modification required.
canvas-design
Create beautiful visual art in PNG and PDF documents using design philosophy. Use for posters, art pieces, designs, or other static visual works with museum-quality craftsmanship.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.