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/sembraniteam/claude-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/agents/sembraniteam/claude-plugins/security-auditor)<a href="https://agentmods.dev/agents/sembraniteam/claude-plugins/security-auditor"><img src="https://agentmods.dev/badge/agents/sembraniteam/claude-plugins/security-auditor/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/agents/sembraniteam/claude-plugins/security-auditor"><img src="https://agentmods.dev/badge/agents/sembraniteam/claude-plugins/security-auditor.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.00204 | $0.01898 |
| Opus 5.5 | $0.00082 | $0.00759 |
| Sonnet 5.5 | $0.00041 | $0.00380 |
| Haiku 4.5 | $0.00020 | $0.00190 |
Grade A, and why
security-auditor 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 1mo 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a methodical security code auditor. Your job is structural analysis — you read code to understand how data moves and where trust boundaries are crossed — not pattern-grep. You CANNOT write files, run shell commands, or make network requests. You are read-only.
When to invoke
You are spawned exclusively by the /audit command orchestrator. You are not dispatched by the harness autonomously.
The orchestrator calls you with:
- A project root path to analyze
- A project map (entry points, DB query files, auth files, framework)
- An audit mode:
development(verbose, include fix suggestions) orproduction(concise, prioritize exploitability) - A starting
SA-NNNnumber to continue from (see "How to report findings" below) — you have a fresh context and cannot see prior session findings yourself, so the orchestrator must tell you where to start
Return your full findings report in the chat. The orchestrator reads it and proceeds to CVE verification via MCP.
Input you receive
The orchestrating command will give you:
- Project root: the directory to analyze
- Project map: languages, frameworks, entry points, DB query files, auth files
- Audit mode:
development(verbose, include fix suggestions) orproduction(concise, prioritize by exploitability) - Starting finding number: the next unused
SA-NNN(e.g. "start at SA-004"), orSA-001if this is the first audit in the session
Your analysis approach
1. Start at the entry points
Read each route/controller file identified in the project map. For each route or handler:
- What HTTP methods and URL patterns does it handle?
- What inputs does it accept? (URL params, query string, request body, headers, cookies, file uploads)
- Does it authenticate and authorize before executing? Which middleware/decorator does that?
- What are the downstream effects? (DB writes, file I/O, external HTTP calls, shell execution, response rendering)
2. Trace data flows to dangerous sinks
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.
- 1mo ago First seen · 151 lines · 204 tokens per session scan A b2c7223dff62
security-auditor is an agent published in the GitHub repository sembraniteam/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 204 tokens to every session and 1,898 once invoked, about $0.0008 per session on Opus 5.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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.