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/attilaszasz/sdd-pilotWrote 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/attilaszasz/sdd-pilot/sddp-adversarial-scanner)<a href="https://agentmods.dev/agents/attilaszasz/sdd-pilot/sddp-adversarial-scanner"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/sddp-adversarial-scanner/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/attilaszasz/sdd-pilot/sddp-adversarial-scanner"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/sddp-adversarial-scanner.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00086 |
| Opus 5 | $0.00010 | $0.00043 |
| Sonnet 5 | $0.00004 | $0.00017 |
| Haiku 4.5 | $0.00002 | $0.00009 |
Grade A, and why
sddp-adversarial-scanner 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 11d 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.
What it actually says
Read and follow the methodology in .github/agents/_adversarial-scanner.md.
Do not ask the user directly. If user input is required, return USER_INPUT_REQUIRED with question, options, and recommended fields to the parent skill.
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.
- 11d ago First seen · 10 lines · 21 tokens per session scan A 809f9fe1df4a
sddp-adversarial-scanner is an agent published in the GitHub repository attilaszasz/sdd-pilot (96 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 86 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-30.
Other agents, from other repositories
Spec-Driven
Use this planner when the user wants implementation to be specified and approved before code changes. Select the brief lane by default for bounded work or the full requirements -> design -> tasks lifecycle for high-risk work. Never implement before the selected lane's approval gate.
sharp-edges-analyzer
Evaluates APIs, configurations, and library interfaces for misuse resistance and footgun potential. Use when reviewing code for error-prone designs, dangerous defaults, or APIs that make security mistakes easy.
sdd-scout
Architecture scout used only by /sdd-architecture-scan. Analyzes one worklist unit and writes its report to .sdd-scan/reports/. Not for general tasks.
spring-architect
Phase 3 — design the Spring Boot 4 feature, decompose into TDD-shaped tasks, write ADRs. Use proactively when the user asks for design, plan, or runs /plan.
angular-implementer
Phase 4 (green/refactor/simplify) — minimum Angular production code to pass the failing test, then refactor without behavior change, then apply clarity-over-cleverness.
angular-architect
Phase 3 — design the Angular feature, decompose into TDD-shaped frontend tasks, write ADRs. Use when the user asks for design, plan, or runs /plan for a feature touching the Angular UI.