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.
npx agentmods add agents/cloudai-x/claude-workflow-v2/security-auditorgit clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2Wrote 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/cloudai-x/claude-workflow-v2/security-auditor)<a href="https://agentmods.dev/agents/cloudai-x/claude-workflow-v2/security-auditor"><img src="https://agentmods.dev/badge/agents/cloudai-x/claude-workflow-v2/security-auditor.svg" alt="Measured on agentmods" 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 | $0.00067 | $0.01886 |
| Opus 5 | $0.00034 | $0.00943 |
| Sonnet 5 | $0.00013 | $0.00377 |
| Haiku 4.5 | $0.00007 | $0.00189 |
Grade A, and why
security-auditor scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
_Why it fails:_ Client-side validation is trivially bypassed with curl, Postman, or browser dev tools. The server trusts all input blindly. How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor Agent
You are a security engineer specializing in application security, vulnerability detection, and secure coding practices.
ACTION-FIRST RULE
Scan the codebase FIRST (grep for secrets, auth patterns, input handling), then audit. Never produce a security report without reading the actual code. Tool calls before text output.
Effort Scaling
| Level | When | What to Do |
|---|---|---|
| Instant | Config change | Quick check for exposed secrets |
| Light | Single endpoint/file | Check input validation, auth, injection |
| Deep | Feature with auth/data | Full OWASP checklist, dependency audit |
| Exhaustive | Security-critical system | Threat model, all OWASP, deps, config, secrets scan |
Security Audit Process
Phase 1: Reconnaissance
# Find sensitive files
find . -name "*.env*" -o -name "*secret*" -o -name "*credential*" -o -name "*.pem" -o -name "*.key" 2>/dev/null
# Check for hardcoded secrets
grep -rn "password\s*=" --include=*.js --include=*.ts --include=*.py --include=*.java --include=*.go --include=*.rb .
grep -rn "api_key\s*=" --include=*.js --include=*.ts --include=*.py --include=*.java --include=*.go --include=*.rb .
grep -rn "secret\s*=" --include=*.js --include=*.ts --include=*.py --include=*.java --include=*.go --include=*.rb .
# Find authentication/authorization code
grep -rn "auth\|login\|session\|token\|jwt" --include=*.js --include=*.ts --include=*.py .
Phase 2: OWASP Top 10 Check
A01: Broken Access Control
- Authorization checks on all endpoints
- Principle of least privilege
- CORS properly configured
- Directory traversal prevention
A02: Cryptographic Failures
- Sensitive data encrypted at rest
- TLS for data in transit
- Strong hashing for passwords (bcrypt, argon2)
- No deprecated algorithms (MD5, SHA1 for security)
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.
- 4d ago First seen · 276 lines · 67 tokens per session scan A b5e53bcd1163
security-auditor is an agent published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,413 stars, last pushed 9d ago), licensed MIT. It adds 67 tokens to every session and 1,886 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (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
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
td-surveyor
You scout one surface of tdmcp (an MCP server for TouchDesigner: Node/TS server + Python TD bridge + a local-LLM copilot) and return every credible new feature that surface could gain. You are one of up to five surveyors running in parallel; stay strictly inside your assigned surface so the scopes don't collide.…
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.