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 skills add morodomi/redteam-skills --skill attack-reportgit 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/skills/morodomi/redteam-skills/attack-report)<a href="https://agentmods.dev/skills/morodomi/redteam-skills/attack-report"><img src="https://agentmods.dev/badge/skills/morodomi/redteam-skills/attack-report.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.00020 | $0.00858 |
| Opus 5 | $0.00010 | $0.00429 |
| Sonnet 5 | $0.00004 | $0.00172 |
| Haiku 4.5 | $0.00002 | $0.00086 |
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 8d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 Structure
# Security Scan Report
## Executive Summary
### リスク評価
| 評価項目 | 結果 |
|----------|------|
| **総合リスク** | High |
| **検出件数** | Critical: 0, High: 2, Medium: 1, Low: 0 |
| **対象システム** | Laravel Application |
### 優先対応 Top 3
| 優先度 | 脆弱性 | CVSS | 対応期限 |
|--------|--------|------|----------|
| 1 | SQL Injection (SQLI-001) | 9.3 | 即時 |
| 2 | XSS (XSS-001) | 7.2 | 1週間以内 |
| 3 | CSRF (CSRF-001) | 5.1 | 次スプリント |
### 影響を受けるシステム
- `app/Controllers/UserController.php`
- `app/Controllers/AuthController.php`
- `resources/views/user.blade.php`
---
## Summary
| Item | Value |
|------|-------|
| Scan ID | <uuid> |
| Scanned At | <timestamp> |
| Target | <path> |
| Framework | Laravel |
### Vulnerability Summary
| Severity | Count |
|----------|-------|
| Critical | 0 |
| High | 2 |
| Medium | 1 |
| Low | 0 |
| **Total** | **3** |
## Vulnerabilities
### Critical (0)
(No critical vulnerabilities found)
### High (2)
#### [SQLI-001] SQL Injection
- **CVSS 4.0**: 9.3 (Critical)
- **Vector**: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`
- **File**: app/Controllers/UserController.php:45
- **Agent**: injection-attacker
- **References**:
- [CWE-89](https://cwe.mitre.org/data/definitions/89.html)
- [OWASP A03:2021](https://owasp.org/Top10/2021/A03_2021-Injection/)
- **Description**: User input concatenated in SQL query
- **Remediation**: Use parameterized queries or ORM
### Medium (1)
...
### Low (0)
...
## Recommendations
1. **High Priority**: Fix all Critical and High severity issues immediately
2. **Medium Priority**: Address Medium issues in next sprint
3. **Low Priority**: Review Low issues during code review
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.
- 8d ago First seen · 133 lines · 20 tokens per session scan A d3ba120a0e68
attack-report is a skill published in the GitHub repository morodomi/redteam-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 858 once invoked, about $0.0001 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
security-expert
Expert-level application security, OWASP Top 10, penetration testing, and security best practices. Use when the user mentions OWASP, pentesting, appsec, vulnerability, encryption, or authentication, or when the task involves Security Principles, OWASP Top 10, Security Domains, or Broken Access Control.
api-secure-report
Full security inventory of every HTTP route in a backend project — each route marked clean or carrying findings, with the exploitation path and the mitigation, written in the user's language (pt-BR by default). Use when the user runs /api-secure-report, or asks for a security report, audit or inventory of the…
penetration-tester
Authorized penetration tester persona — offensive security specialist for network, web app, cloud, and Active Directory assessments. Requires explicit authorization.
Mixed-Language Monorepos
This skill should be used when the user is auditing a "polyglot monorepo", "multi-language codebase", "microservices with different languages", "Go + Python + TypeScript", or any codebase with services written in different programming languages. Provides strategies for cross-service security analysis and unified…
OWASP API Security Top 10
This skill should be used when the user asks about "API security", "OWASP API Top 10", "BOLA", "broken object level authorization", "API authentication", "mass assignment", "GraphQL security", "gRPC security", "rate limiting", "API abuse", "REST API vulnerabilities", or needs to identify API-specific security issues…
Cache Poisoning
This skill should be used when the user asks about "cache poisoning", "web cache deception", "CDN cache", "proxy cache", "nginx cache", "varnish", "cache key manipulation", "response caching", or needs to find cache-related vulnerabilities during whitebox security review.