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 skills/morodomi/dev-crew/attack-reportnpx skills add morodomi/dev-crew --skill attack-reportgit 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.00106 | $0.00519 |
| Opus 5 | $0.00053 | $0.00260 |
| Sonnet 5 | $0.00021 | $0.00104 |
| Haiku 4.5 | $0.00011 | $0.00052 |
Grade A, and why
attack-report 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.
What it actually says
Attack Report
security-scan結果をMarkdownレポート形式で出力するスキル。
Usage
/attack-report # 直前のsecurity-scan結果をレポート化
/attack-report ./report.md # 指定ファイルに出力
Input Format
security-scan が出力するJSON形式を入力として受け取る。
{
"metadata": {
"scan_id": "<uuid>",
"scanned_at": "<timestamp>",
"target_directory": "<path>"
},
"recon": {
"framework": "Laravel",
"endpoints_count": 15,
"high_priority_count": 5
},
"summary": {
"total": 3,
"critical": 0,
"high": 2,
"medium": 1,
"low": 0
},
"vulnerabilities": [...]
}
Output Format
Markdown形式のレポートを生成。脆弱性はCVSSスコア降順でソート。
Report Sections
| Section | Content |
|---|---|
| Executive Summary | リスク評価、優先対応Top 3、影響システム |
| Summary | スキャンメタデータ、脆弱性件数サマリ |
| Vulnerabilities | 重大度別の脆弱性一覧 (Critical -> Low) |
| Recommendations | 対応優先度に基づく推奨事項 |
Vulnerability Entry
各脆弱性は以下を含む:
- ID, Type, CVSS 4.0 Score/Vector
- File and line number
- Agent, CWE/OWASP references
- Description, Remediation
Reference
詳細・レポートテンプレート: reference.md
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 69 lines · 106 tokens per session scan A 25bd07677684
attack-report is a skill published in the GitHub repository morodomi/dev-crew (1 stars, last pushed 3d ago), licensed MIT. It adds 106 tokens to every session and 519 once invoked, about $0.0005 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 skills, from other repositories
software-test-execution
Run scoped tests for a TDD slice, determine the appropriate test framework and command, and report structured pass/fail results. Use when tests need to be executed after writing, implementing, or refactoring code. Reads test metadata, discovers the test framework if needed, executes the scoped test command, parses…
nw-at-completeness-check
Canonical AT completeness gate — research-anchored 7-category taxonomy (C1-C7) + 15-item mechanical checklist. Paradigm-neutral. Drives acceptance-designer reviewer verdict deterministically.
nw-ab-critique-dimensions
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation.
nw-bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
software-code-refactoring
Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…
nw-canary
Canary skill for auto-injection detection.