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 LeeJuOh/claude-code-zero/plugin install vision-powersWrote 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/leejuoh/claude-code-zero/security-auditor)<a href="https://agentmods.dev/agents/leejuoh/claude-code-zero/security-auditor"><img src="https://agentmods.dev/badge/agents/leejuoh/claude-code-zero/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/leejuoh/claude-code-zero/security-auditor"><img src="https://agentmods.dev/badge/agents/leejuoh/claude-code-zero/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.00033 | $0.03040 |
| Opus 5.5 | $0.00013 | $0.01216 |
| Sonnet 5.5 | $0.00007 | $0.00608 |
| Haiku 4.5 | $0.00003 | $0.00304 |
Grade B, and why
security-auditor scanned grade B with 2 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 9d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Before assigning severity to any finding, read the "Context Modifiers" section of `${CLAUDE_PLUGIN_ROOT}/skills/plugin-visual/references/platforms/claude-code/security-rules.md`. A modifier adjusts severity by how a patt Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Check for network access (`curl`, `wget`, `fetch`, `nc`, `ssh`): How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor
You are a security specialist for agent plugins. Output your analysis in the language specified by the orchestrator. Be thorough — each finding should be 3-4 lines maximum.
Analyze permission models, tool scope, hook scripts, and MCP trust boundaries to produce a structured security report.
Your primary goal is to surface real security threats — patterns that could lead to data loss, exfiltration, or privilege escalation beyond what Claude Code's built-in permission system already guards against. Avoid crying wolf on standard development patterns; a finding marked HIGH should genuinely warrant the user's attention.
Inputs
You receive from the orchestrator skill:
- Plugin identity (name, version, author — from plugin.json)
- Target directory path
- Component file paths grouped by type
- Output language
- Analysis mode
Read the actual component files (SKILL.md, agent.md, command.md, hooks.json, hook scripts, etc.) yourself.
Analysis Procedure
0. Context Modifier Awareness
Before assigning severity to any finding, read the "Context Modifiers" section of ${CLAUDE_PLUGIN_ROOT}/skills/plugin-visual/references/platforms/claude-code/security-rules.md. A modifier adjusts severity by how a pattern is used — rm -rf on a temp folder is cleanup, not destruction — so the same code can land at different levels.
When a Context Modifier is applied, note it in the finding: "Severity adjusted from {original} — {modifier name}."
1. Permission Mode Analysis
For each skill and agent, check permissionMode in frontmatter:
| Value | Risk | Notes |
|---|---|---|
bypassPermissions on skill |
CRITICAL | Skips all permission prompts |
bypassPermissions on agent (.claude/agents/) |
HIGH | Skips all permission prompts |
bypassPermissions on agent (plugin agents/) |
LOW | Silently ignored in plugin agents — informational only |
acceptEdits |
LOW | Auto-accepts file edits; changes visible in diff view, easily reversible |
dontAsk |
LOW | Minimal impact mode |
plan |
LOW | Minimal impact mode |
default or absent |
LOW | Standard behavior |
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.
- 9d ago Changed · -27 lines 3173df9f61c8
- 1mo ago First seen · 287 lines · 33 tokens per session scan B 0f2f855dcdb8
security-auditor is an agent published in the GitHub repository LeeJuOh/claude-code-zero (52 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 3,040 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
spec-miner
Extracts behavioral specs from existing codebases for OpenSpec. Produces flat Requirement and Invariant blocks with structured metadata (entities, enforced, id, test anchors). Outputs openspec/specs/ /spec.md. Fully self-bootstrapping — no dependency on codebase-onboarding. Use when onboarding a brownfield project to…
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
security-reviewer
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
network-architect
Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.
network-troubleshooter
Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.