dynamic-verifier

An agent that dynamically checks suspected web security problems by sending controlled requests to a running website. It covers SQL injection, cross-site scripting, authentication, request-forgery, server-side request forgery, and file-reading checks.

In plain words
What is it for?
It verifies suspected flaws using non-destructive test inputs and checks responses or callbacks for evidence.
Why use it?
Static analysis can report a possible security flaw without proving it works; these checks test whether the running site actually responds in the vulnerable way.

Agent

Install

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.

agentmods
npx agentmods add agents/morodomi/dev-crew/dynamic-verifier
Clone the repo
git clone --depth 1 https://github.com/morodomi/dev-crew
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,400 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00036 $0.02400
Opus 5 $0.00018 $0.01200
Sonnet 5 $0.00007 $0.00480
Haiku 4.5 $0.00004 $0.00240

Measured yesterday against content hash ab9e7197847f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

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.

`curl -i` | Content-Type: allow `text/html*`, skip `application/json|text/xml|application/xml` | redirect: `-L`, max 5
agents/dynamic-verifier.md · 292 lines

How it starts

The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Common Settings

rate_limiting: 2s, max_requests: 50, timeout: 10s, connect_timeout: 5s

Common Pre-processing

curl -i | Content-Type: allow text/html*, skip application/json|text/xml|application/xml | redirect: -L, max 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_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

Safety Measures

Risk Mitigation Implementation
Production attack --target required Exit if URL not specified
Destructive payload Non-destructive only Check against forbidden list
Overload Rate limiting sleep 1 between requests
Unintended attack URL validation Confirm if not localhost

URL Validation Logic

url_validation:
  allowed_schemes: [http, https]
  safe_hosts: [localhost, 127.0.0.1, "::1", "[::1]"]  # 0.0.0.0 excluded (production risk)
  confirmation_required: "All other hosts → WARNING: Target is not localhost. Continue? (y/N)"

Read the full file on GitHub · 292 lines

Changes

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.

  1. yesterday First seen · 292 lines · 36 tokens per session scan C ab9e7197847f

Subscribe to this mod's changes

dynamic-verifier is an agent published in the GitHub repository morodomi/dev-crew (1 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 2,400 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.