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/api-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.00033 | $0.00691 |
| Opus 5 | $0.00016 | $0.00345 |
| Sonnet 5 | $0.00007 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
api-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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detection Targets
| Type | Description | Pattern |
|---|---|---|
| Mass Assignment | 一括代入脆弱性 | $request->all(), fillable未定義 |
| BOLA | オブジェクトレベル認可不備 | IDパラメータの権限チェック漏れ |
| Rate Limiting | レート制限なし | throttle未設定のAPI |
| Excessive Data Exposure | 過剰なデータ露出 | 全カラム返却、機密フィールド露出 |
Framework Detection Patterns
| Framework | Vulnerable Pattern | Safe Pattern |
|---|---|---|
| Laravel | $request->all(), Model::create($input) |
$request->only(), $fillable |
| Django | Model(**request.data) |
Serializer with fields |
| Flask | Model(**request.json) |
Schema validation |
| Express | Model.create(req.body) |
Validation middleware |
Dangerous Patterns
patterns:
# Mass Assignment
- '\$request->all\s*\(\)'
- 'Model::create\s*\(\s*\$request'
- '\*\*request\.(data|json)'
- 'create\s*\(\s*req\.body\s*\)'
# BOLA - Missing ownership check
- 'find\s*\(\s*\$id\s*\)'
- 'findOrFail\s*\(\s*\$'
- 'get_object_or_404\s*\('
# Rate Limiting Missing
- 'Route::.*->middleware\s*\([^)]*(?!throttle)'
# Excessive Data Exposure
- 'return\s+\$\w+->toArray\s*\(\)'
- '->get\s*\(\)\s*$'
- 'SELECT\s+\*\s+FROM'
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=API, types=mass-assignment|bola|rate-limiting|excessive-data-exposure
Severity Criteria
| Severity | Criteria |
|---|---|
| critical | BOLA on sensitive resources (admin, payment) |
| high | Mass Assignment, Excessive Data Exposure |
| medium | Rate Limiting missing on auth endpoints |
| low | Rate Limiting missing on public endpoints |
CWE/OWASP Mapping
| Reference | ID |
|---|---|
| CWE | CWE-915: Mass Assignment |
| CWE | CWE-639: IDOR/BOLA |
| OWASP API Top 10 | API1:2023 BOLA |
| OWASP API Top 10 | API3:2023 Broken Object Property Level Authorization |
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 · 76 lines · 33 tokens per session scan A cbd2366ee4ca
api-attacker is an agent published in the GitHub repository morodomi/dev-crew (1 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 691 once invoked, about $0.0002 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 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.