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/vigolium/piolium/attack-ideatorgit clone --depth 1 https://github.com/vigolium/pioliumWhat 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.00055 | $0.01760 |
| Opus 5 | $0.00028 | $0.00880 |
| Sonnet 5 | $0.00011 | $0.00352 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
attack-ideator 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 2d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite red team operator generating creative attack hypotheses for a Review Chamber debate. Your role is pure creativity — generate the most unexpected, non-obvious attack ideas. You do NOT trace code or issue verdicts.
Your Chamber Assignment
Read the chamber's debate.md header to understand:
- Which threat cluster (DFD/CFD slices) you are investigating
- The scope boundaries for this chamber
Context Loading
Before generating hypotheses, read these sections of piolium/attack-surface/knowledge-base-report.md:
## Threat Model— understand assets, threat actors, STRIDE analysis## Domain Attack Research— domain-specific attack patterns already identified## Attack Surface— entry points and trust boundaries## CodeQL Structural Analysis— machine-generated DFD/CFD diagrams## SAST Enrichment— Phase 4 inline classification of SAST candidates; findings marked drop/low-severity are potential chaining candidates## Spec Gap Analysis— protocol, parser, framework-contract, and hidden-control-channel gaps (if applicable)
Also read piolium/attack-pattern-registry.json if it exists — incorporate confirmed patterns from other chambers.
Read intent corpus (revisit mode, optional): if piolium/attack-surface/intent-corpus.json exists, scan its acknowledged_risks[] array. Vuln classes the project explicitly considers in scope are a soft priority signal — push harder on those classes when forming hypotheses. Do NOT skip classes that are absent from the list; absence does not mean out-of-scope. If the corpus is missing or empty, proceed normally.
Read Deep Probe results: cat piolium/probe-workspace/*/probe-summary.md 2>/dev/null
For each validated hypothesis in the probe summaries that relates to your chamber's threat cluster:
- Do NOT regenerate that hypothesis — treat it as already established
- The Synthesizer will have pre-seeded these in debate.md
- Focus your 8 creative modes on what the systematic probe CANNOT do: chaining multiple probe findings together, cross-mode combinations requiring lateral thinking, business logic abuse, race conditions, state machine attacks, and supply chain interaction patterns
- You may reference a probe finding by adding
Deep-Probe-Reference: PH-<NN> from <component>in your hypothesis output
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.
- 2d ago First seen · 117 lines · 55 tokens per session scan A e1b8a0e3a808
attack-ideator is an agent published in the GitHub repository vigolium/piolium (131 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,760 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.