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 commands/rcdelacruz/claude-code-agents/workflow-review-securitygit clone --depth 1 https://github.com/rcdelacruz/claude-code-agentsWrote 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/commands/rcdelacruz/claude-code-agents/workflow-review-security)<a href="https://agentmods.dev/commands/rcdelacruz/claude-code-agents/workflow-review-security"><img src="https://agentmods.dev/badge/commands/rcdelacruz/claude-code-agents/workflow-review-security.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.00013 | $0.02409 |
| Opus 5 | $0.00006 | $0.01205 |
| Sonnet 5 | $0.00003 | $0.00482 |
| Haiku 4.5 | $0.00001 | $0.00241 |
Grade A, and why
workflow-review-security 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 5d 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.
const response = await fetch(url) How it starts
The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are in SECURITY REVIEW MODE.
Use security agent to perform thorough security audit.
Security Audit Process
1. OWASP Top 10 Review (30 mins)
A01: Broken Access Control
// ❌ CRITICAL: No authorization check
export async function deletePost(id: string) {
await db.post.delete({ where: { id } })
}
// ✅ SECURE: Proper authorization
export async function deletePost(id: string) {
const session = await auth()
if (!session?.user) {
throw new UnauthorizedError()
}
const post = await db.post.findUnique({
where: { id },
select: { authorId: true }
})
if (!post) {
throw new NotFoundError()
}
if (post.authorId !== session.user.id && session.user.role !== 'ADMIN') {
throw new ForbiddenError()
}
await db.post.delete({ where: { id } })
}
Checklist:
- All protected routes check authentication
- Resource ownership verified before operations
- Role-based access control (RBAC) implemented
- No client-side authorization only
- API endpoints protected with middleware
A02: Cryptographic Failures
// ❌ CRITICAL: Storing plain text passwords
await db.user.create({
data: { email, password } // Plain text!
})
// ✅ SECURE: Hashed passwords
import bcrypt from 'bcrypt'
const hashedPassword = await bcrypt.hash(password, 12)
await db.user.create({
data: { email, password: hashedPassword }
})
Checklist:
- Passwords hashed with bcrypt (12+ rounds)
- HTTPS enforced in production
- Sensitive data encrypted at rest
- Secure session storage
- Environment variables for secrets
- No secrets in code or version control
A03: Injection
// ❌ CRITICAL: SQL injection risk (raw SQL)
const userId = req.query.id // User controlled!
await db.$executeRaw`SELECT * FROM users WHERE id = ${userId}`
// ✅ SECURE: Parameterized query
const userId = req.query.id
await db.user.findUnique({ where: { id: userId } })
// ✅ SECURE: Input validation
const validated = z.string().cuid().parse(userId)
await db.user.findUnique({ where: { id: validated } })
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.
- 5d ago First seen · 400 lines · 13 tokens per session scan A 3707b4444a67
workflow-review-security is a command published in the GitHub repository rcdelacruz/claude-code-agents (2 stars, last pushed 10mo ago), licensed MIT. It adds 13 tokens to every session and 2,409 once invoked, about $0.0001 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.