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/iwritec0de/app-dev/auth-auditgit clone --depth 1 https://github.com/iwritec0de/app-devWhat 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.00008 | $0.01020 |
| Opus 5 | $0.00004 | $0.00510 |
| Sonnet 5 | $0.00002 | $0.00204 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
auth-audit 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 yesterday.
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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auth Audit
Scan the project's authentication and authorization implementation for security vulnerabilities.
Load the auth-patterns skill for authentication and authorization security patterns.
Usage
/auth-audit [--focus jwt|session|oauth|rbac|all]
Arguments
Parse $ARGUMENTS to extract:
- --focus (optional, default:
all)jwt— JWT implementation issuessession— Session management issuesoauth— OAuth2 implementation issuesrbac— Role/permission issuesall— Audit everything
Instructions
1. Detect Auth Implementation
Search for auth patterns:
grep -rn "jsonwebtoken\|jose\|jwt\|JWT" --include="*.ts" --include="*.js" 2>/dev/null
grep -rn "bcrypt\|argon2\|scrypt\|pbkdf2" --include="*.ts" --include="*.js" 2>/dev/null
grep -rn "passport\|next-auth\|lucia\|clerk\|auth0\|supabase.*auth" --include="*.ts" --include="*.js" 2>/dev/null
grep -rn "session\|cookie\|Set-Cookie" --include="*.ts" --include="*.js" 2>/dev/null
grep -rn "role\|permission\|authorize\|canAccess\|isAdmin" --include="*.ts" --include="*.js" 2>/dev/null
2. JWT Audit
If JWT is used, check for:
Critical:
- Weak or hardcoded secret key (secret in source code, short key,
"secret") - Algorithm confusion (accepting
none, not verifyingalgheader) - Missing token expiration (
expclaim) - Token stored in localStorage (XSS-accessible)
- Secret in client-side code
High:
- No token refresh mechanism (long-lived access tokens)
- Missing
iss(issuer) validation - Missing
aud(audience) validation - Token not invalidated on password change
- No token revocation mechanism (logout doesn't invalidate)
Medium:
- Using HS256 when RS256 is more appropriate (multi-service)
- Excessive token payload (PII, roles should be verified server-side)
- Missing
jtifor token uniqueness
3. Password Audit
Check for:
- Weak hashing (MD5, SHA1, SHA256 without salt)
- Missing salt (even with bcrypt, verify rounds ≥ 10)
- Password stored in plaintext
- No minimum password requirements enforced
- Missing rate limiting on login endpoint
- Missing account lockout after failed attempts
- Password comparison using
===instead of timing-safe compare
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.
- yesterday First seen · 130 lines · 8 tokens per session scan A 9043e7dfa02f
auth-audit is a command published in the GitHub repository iwritec0de/app-dev (3 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 1,020 once invoked, about $0.0000 per session on Opus 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 commands, from other repositories
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
better-auth:add-plugin
Add a better-auth plugin to an existing project. Configures server and client plugins with proper imports.
sheet-report
Analyze a Numbers or Excel file and generate a report with charts.
numbers-to-excel
Convert a Numbers document to Excel.
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
add-skill
Add a new Skill to the current plugin with proper structure.