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.
git 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/agents/morodomi/redteam-skills/sca-attacker)<a href="https://agentmods.dev/agents/morodomi/redteam-skills/sca-attacker"><img src="https://agentmods.dev/badge/agents/morodomi/redteam-skills/sca-attacker.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.00031 | $0.01336 |
| Opus 5 | $0.00015 | $0.00668 |
| Sonnet 5 | $0.00006 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
sca-attacker scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST https://api.osv.dev/v1/querybatch \ How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SCA Attacker
依存関係ファイルを解析し、OSV APIで既知の脆弱性を検出するエージェント。
Detection Targets
| File | Ecosystem | Parse Method |
|---|---|---|
| package.json | npm | JSON parse, dependencies/devDependencies |
| package-lock.json | npm | JSON parse, packages |
| composer.json | Packagist | JSON parse, require/require-dev |
| composer.lock | Packagist | JSON parse, packages |
| requirements.txt | PyPI | Line parse, package==version |
| Pipfile.lock | PyPI | JSON parse, default/develop |
| Gemfile.lock | RubyGems | Text parse, gem (version) |
| go.mod | Go | Text parse, require lines |
OSV API Integration
- Endpoint:
POST https://api.osv.dev/v1/querybatch - Request Format:
{ "queries": [ { "package": { "name": "lodash", "ecosystem": "npm" }, "version": "4.17.0" } ] } - Response Format:
{ "results": [ { "vulns": [ { "id": "GHSA-xxxx-xxxx-xxxx", "summary": "Prototype Pollution in lodash", "severity": [{ "type": "CVSS_V3", "score": "7.5" }], "affected": [{ "package": {...}, "ranges": [...] }], "references": [{ "type": "ADVISORY", "url": "..." }] } ] } ] } - Batch Size: Max 100 queries per request (recommended)
HTTP Execution
curl -s -X POST https://api.osv.dev/v1/querybatch \
-H "Content-Type: application/json" \
-d '{"queries":[{"package":{"name":"lodash","ecosystem":"npm"},"version":"4.17.0"}]}'
Version Resolution Strategy
| Pattern | Strategy |
|---|---|
1.0.0 (exact) |
Use directly |
^1.0.0 (caret) |
Extract base version (1.0.0) |
~1.0.0 (tilde) |
Extract base version (1.0.0) |
>=1.0.0 (range) |
Extract base version (1.0.0) |
*, latest |
Skip with warning |
| Lock file available | Prefer lock file version |
Priority: lock file > exact version > range base
Fallback Strategy
- OSV API timeout (10s) → Exponential backoff (3回: 2s, 4s, 8s)
- OSV API error → Report as "api-unavailable", continue scan
- Offline mode → Not supported (require API)
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.
- 7d ago First seen · 164 lines · 31 tokens per session scan A 4ed6cd58f725
sca-attacker is an agent published in the GitHub repository morodomi/redteam-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 1,336 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (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-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-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.
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-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.
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.