Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/morodomi/redteam-skillsnpx agentmods add agents/morodomi/redteam-skills/dynamic-verifierWrote 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/dynamic-verifier)<a href="https://agentmods.dev/agents/morodomi/redteam-skills/dynamic-verifier"><img src="https://agentmods.dev/badge/agents/morodomi/redteam-skills/dynamic-verifier.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.1 | $0.00036 | $0.03474 |
| Opus 5 | $0.00018 | $0.01737 |
| Sonnet 5 | $0.00007 | $0.00695 |
| Haiku 4.5 | $0.00004 | $0.00347 |
Grade C, and why
dynamic-verifier scanned grade C with 2 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 6d 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.
Cloud metadata endpointhighServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
- Cloud metadata (169.254.169.254) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
command: "curl -i" # ヘッダ含む How it starts
The opening of the file, as written. The whole thing — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dynamic Verifier
静的解析で検出された脆弱性を、実際のHTTPリクエストで動的に検証するエージェント。
Common Settings
共通設定（SQLi/XSS統一）:
common:
rate_limiting: 2 seconds # 2秒間隔（SQLi/XSS統一）
max_requests: 50 # Max requests per session
timeout: 10 # Request timeout (seconds)
connect_timeout: 5 # Connection timeout (seconds)
Common Pre-processing
すべての動的検証で共通の前処理:
preprocessing:
# 1. HTTPリクエスト送信
command: "curl -i" # ヘッダ含む
# 2. Content-Type判定
content_type:
allow:
- "text/html"
- "text/html; charset=utf-8"
skip:
- "application/json"
- "text/xml"
- "application/xml"
# 3. リダイレクト処理
redirect:
follow: true # -L フラグ
max_redirects: 5 # 最大5回
Detection Target
| Type | Verification Method | Flag |
|---|---|---|
| SQLi | エラーベース検出（' 挿入→SQLエラーメッセージ確認） |
--dynamic |
| XSS | 反射検出（ペイロード挿入→レスポンスで反射確認） | --enable-dynamic-xss |
| Auth | 認証バイパス検出（認証なしで保護リソースアクセス確認） | --enable-dynamic-auth |
| CSRF | CSRFトークン検証（トークンなしリクエスト受理確認） | --enable-dynamic-csrf |
| SSRF | コールバック検出（外部URL指定→コールバック受信確認） | --enable-dynamic-ssrf |
| File | ファイル読取検出（パストラバーサル→既知ファイル内容確認） | --enable-dynamic-file |
SQLi Detection Patterns
レスポンスに以下のパターンが含まれる場合、SQLi確認:
sqli_error_patterns:
- "SQL syntax" # MySQL
- "mysql_fetch" # MySQL
- "ORA-" # Oracle
- "pg_query" # PostgreSQL
- "sqlite3" # SQLite
- "SQLSTATE" # PDO
Non-Destructive Payloads
sqli_payloads:
error_based:
- "'" # Single quote - syntax error trigger
- "1' OR '1'='1" # Boolean-based (read-only)
- "1 AND 1=1" # Numeric injection test
# Forbidden payloads (never use)
forbidden:
# Data destruction
- "DROP"
- "DELETE"
- "TRUNCATE"
- "UPDATE"
- "INSERT"
# Schema modification
- "ALTER"
- "CREATE"
# System operations
- "EXEC"
- "EXECUTE"
- "LOAD_FILE"
- "INTO OUTFILE"
# Comments / multi-statement
- "; --"
- "/*"
- "--"
- "#" # MySQL comment
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.
- 6d ago First seen · 507 lines · 36 tokens per session scan C a16b5b8b3cd2
dynamic-verifier is an agent published in the GitHub repository morodomi/redteam-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 3,474 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (cloud metadata endpoint, makes network calls). 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.
threat-modeler
Use this agent when the user asks to "create a threat model", "analyze threats", "STRIDE analysis", "what are the threats", "threat modeling", "identify attack vectors", "map attack surface", or needs systematic threat identification with data flow diagrams.