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/morodomi/dev-crew/auth-attackergit clone --depth 1 https://github.com/morodomi/dev-crewWhat 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.00037 | $0.00735 |
| Opus 5 | $0.00018 | $0.00367 |
| Sonnet 5 | $0.00007 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
auth-attacker 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.
This is a copy
86% identical to auth-attacker — 47 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detection Targets
| Type | Description | Pattern |
|---|---|---|
| Hardcoded Credentials | ハードコードされた認証情報 | パスワード/APIキー直書き |
| Missing Auth Check | 認証チェック漏れ | ミドルウェア/ガード不在 |
| Broken Access Control | 認可チェック漏れ | 権限確認なしのリソースアクセス |
| Weak Session | 弱いセッション管理 | 短いセッションID、HTTPのみクッキー |
Framework Detection Patterns
| Framework | Vulnerable Pattern | Safe Pattern |
|---|---|---|
| Laravel | Route without middleware, Auth::check() missing |
->middleware('auth'), Gate/Policy |
| Django | View without @login_required |
@login_required, PermissionRequiredMixin |
| Flask | Route without @login_required |
Flask-Login decorators |
| Express | Route without auth middleware | passport.authenticate(), jwt middleware |
Dangerous Patterns
patterns:
# Hardcoded Credentials
- 'password\s*=\s*["\'][^"\']+["\']'
- 'api_key\s*=\s*["\'][^"\']+["\']'
- 'secret\s*=\s*["\'][^"\']+["\']'
- 'token\s*=\s*["\'][A-Za-z0-9]{20,}["\']'
# Missing Auth (Laravel)
- 'Route::(get|post|put|delete)\s*\([^)]+\)\s*;'
# Missing Auth (Django)
- 'def\s+\w+\s*\(request[^)]*\):'
# Missing Auth (Express)
- 'app\.(get|post|put|delete)\s*\([^,]+,\s*\(req'
# Weak Session
- 'session\.cookie_secure\s*=\s*False'
- 'SESSION_COOKIE_SECURE\s*=\s*False'
- 'cookie:\s*\{\s*secure:\s*false'
Output
Base: {metadata: {scan_id, scanned_at, agent}, vulnerabilities: [{id, type, vulnerability_class, cwe_id, severity, file, line, code, description, remediation}], summary: {total, critical, high, medium, low}}
Extra: prefix=AUTH, types=hardcoded-credentials|missing-auth|broken-access-control|weak-session
Severity Criteria
| Severity | Criteria |
|---|---|
| critical | Hardcoded credentials in production config |
| high | Missing auth on sensitive endpoints |
| medium | Weak session configuration |
| low | Potential auth pattern issue |
CWE/OWASP Mapping
| Reference | ID |
|---|---|
| CWE | CWE-287: Improper Authentication |
| CWE | CWE-862: Missing Authorization |
| OWASP Top 10 | A01:2021 Broken Access Control |
| OWASP Top 10 | A07:2021 Identification and Authentication Failures |
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 · 77 lines · 37 tokens per session scan A ea3d2ea8d4fe
auth-attacker is an agent published in the GitHub repository morodomi/dev-crew (1 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 735 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to auth-attacker, differing in 47 lines, and is treated as a copy.
Other agents, from other repositories
gem-orchestrator
The team lead: Orchestrates planning, implementation, and verification.
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
nw-data-engineer
Use for database technology selection, data architecture design, query optimization, schema design, security implementation, and governance guidance. Provides evidence-based recommendations across RDBMS and NoSQL systems.
nw-ddd-architect
Use for DESIGN wave domain modeling. Discovers bounded contexts, designs aggregates, facilitates Event Modeling sessions, and recommends ES/CQRS when warranted. Writes to architecture SSOT.