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/xss-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.00034 | $0.00887 |
| Opus 5 | $0.00017 | $0.00443 |
| Sonnet 5 | $0.00007 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
xss-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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detection Targets
| Type | Description | Pattern |
|---|---|---|
| Reflected XSS | ユーザー入力の直接出力 | エスケープなしのecho/print |
| DOM XSS | クライアントサイドでのDOM操作 | innerHTML, document.write等 |
| Stored XSS | DB保存後の出力 | 保存→取得→エスケープなし出力 |
| Sanitization Missing | サニタイズ不備 | htmlspecialchars等の欠如 |
Framework Detection Patterns
| Framework | Vulnerable Pattern | Safe Pattern |
|---|---|---|
| Laravel | {!! $input !!}, echo $input |
{{ $input }}, e($input) |
| Django | |safe, mark_safe() |
自動エスケープ（デフォルト） |
| Flask | |safe, Markup() |
自動エスケープ（Jinja2） |
| Express | res.send(input), innerHTML= |
テンプレートエンジン使用 |
Dangerous Patterns
patterns:
# PHP/Laravel
- 'echo\s+\$'
- 'print\s+\$'
- '\{\!\!\s*\$.*\!\!\}'
- '->with\s*\([^)]*\$_'
# Python/Django/Flask
- '\|safe'
- 'mark_safe\s*\('
- 'Markup\s*\('
# Node.js/Express
- 'res\.send\s*\([^)]*\+'
- 'innerHTML\s*='
- 'document\.write\s*\('
DOM XSS Dangerous Patterns
| Category | Sink | Pattern |
|---|---|---|
| DOM操作 | innerHTML | \.innerHTML\s*= |
| DOM操作 | outerHTML | \.outerHTML\s*= |
| DOM操作 | document.write | document\.write\s*\( |
| 実行系 | eval | eval\s*\(.*location |
| jQuery | html() | \.html\s*\( |
| jQuery | append() | \.append\s*\( |
Sources（トレース対象）:
location.hash,location.searchdocument.URL,document.referrerwindow.name
Stored XSS Detection Patterns
| Framework | Save Pattern | Display Pattern |
|---|---|---|
| Laravel | ->create($request->all()) |
{!! $model->field !!} |
| Django | .objects.create(**request.POST) |
{{ field|safe }} |
| Express | collection.insertOne(req.body) |
innerHTML = data.field |
NOTE: 静的解析の限界上、保存と表示の紐付けは同一モデル/変数名での推定。
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=XSS, types=reflected|dom|stored
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 · 97 lines · 34 tokens per session scan A 53ee3804b0e0
xss-attacker is an agent published in the GitHub repository morodomi/dev-crew (1 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 887 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.