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/redteam-skills/api-attackergit clone --depth 1 https://github.com/morodomi/redteam-skillsWrote 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/morodomi/redteam-skills/api-attacker)<a href="https://agentmods.dev/agents/morodomi/redteam-skills/api-attacker"><img src="https://agentmods.dev/badge/agents/morodomi/redteam-skills/api-attacker.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.00033 | $0.00901 |
| Opus 5 | $0.00016 | $0.00451 |
| Sonnet 5 | $0.00007 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
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 3d 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.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Attacker
API固有の脆弱性を静的解析で検出するエージェント。
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 Format
{
"metadata": {
"scan_id": "<uuid>",
"scanned_at": "<timestamp>",
"agent": "api-attacker"
},
"vulnerabilities": [
{
"id": "API-001",
"type": "mass-assignment",
"vulnerability_class": "mass-assignment",
"cwe_id": "CWE-915",
"severity": "high",
"file": "app/Http/Controllers/UserController.php",
"line": 34,
"code": "User::create($request->all())",
"description": "Mass assignment vulnerability - all request data passed to create",
"remediation": "Use $request->only(['name', 'email']) or define $fillable"
}
],
"summary": {
"total": 1,
"critical": 0,
"high": 1,
"medium": 0,
"low": 0
}
}
Severity Criteria
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.
- 3d ago First seen · 111 lines · 33 tokens per session scan A b0521a22ecbc
api-attacker is an agent published in the GitHub repository morodomi/redteam-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 901 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
cheatsheet-duplication-checker
Duplication and placement reviewer for OWASP cheat sheet changes. Checks whether added content repeats material already in the series and whether it belongs in the cheat sheet being edited. Invoked by /review-cheatsheet-pr.
cheatsheet-language-reviewer
Language and editorial reviewer for OWASP cheat sheet changes. Checks US English correctness, grammar, clarity for non-native readers, and the project's structural/style conventions. Invoked by /review-cheatsheet-pr.
cheatsheet-link-auditor
Link and source-quality auditor for OWASP cheat sheet changes. Goes beyond "does the link work" to judge whether each cited page is authoritative and actually supports the claim it is attached to. Invoked by /review-cheatsheet-pr.
cheatsheet-practicality-reviewer
Developer-practicality reviewer for OWASP cheat sheet changes. Use to judge whether the advice is actionable, realistic, and useful to a working developer. Invoked by /review-cheatsheet-pr.
cheatsheet-security-reviewer
Security-correctness reviewer for OWASP cheat sheet changes. Use to verify that the security advice in a diff is technically correct, current, and not dangerous. Invoked by /review-cheatsheet-pr.
appsec-threat-renderer
INTERNAL renderer for Stage 2 of create-threat-model. Invoke only from the skill after Stage 1 has produced validated intermediate artifacts.