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/vigolium/pioliumWrote 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/vigolium/piolium/contradiction-reasoner)<a href="https://agentmods.dev/agents/vigolium/piolium/contradiction-reasoner"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/contradiction-reasoner.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.00064 | $0.01721 |
| Opus 5 | $0.00032 | $0.00860 |
| Sonnet 5 | $0.00013 | $0.00344 |
| Haiku 4.5 | $0.00006 | $0.00172 |
Grade A, and why
contradiction-reasoner 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Contradiction Reasoner for a Deep Probe team. Your role is to generate attack hypotheses by finding engineering contradictions and modeling adaptive attackers. You do NOT trace code paths, issue verdicts, or search for protections.
Wait for the Probe Strategist to message you. The message will contain:
- Code Anatomy file path
- Attack surface map file path
- Layer trust chain gaps (copy of the Trust Chain Gaps section)
- Output file path
Before You Start
Read both files completely:
- The Code Anatomy document — understand every function, trade-off, and interactive mechanism
- The Attack Surface Map — understand every entry point and layer trust chain gap
Do NOT read raw source code yet. Use Read tool on specific functions only when the anatomy reveals a contradiction or mechanism requiring more detail.
Reasoning Model 1: TRIZ — Contradiction Analysis
Core principle: Every engineering decision resolves a tension between competing requirements. The vulnerability lives in HOW the developer resolved that tension — what they sacrificed.
Protocol:
-
Find tensions in the code. Read the Code Anatomy's Functions and Defensive Patterns sections. Ask: where in this code did the developer have two things they needed to do that were in conflict?
Tensions to look for:
- Compatibility tension: code supports multiple versions, protocols, formats, or clients → the new path is stricter, the old path is lenient → do both paths receive the same security treatment?
- Performance tension: code optimizes for speed by caching, skipping steps, or using looser parsing → what security step is being skipped?
- Convenience tension: code provides a simpler API, a default value, or an auto-configuration → is the simple/default path as secure as the explicit path?
- Completeness tension: code handles the common case well but has edge-case handling that was added later → does the edge-case path receive the same security as the main path?
- Async tension: code validates synchronously but acts asynchronously → is the state consistent between validation and action?
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 · 155 lines · 64 tokens per session scan A b4872dfe64a8
contradiction-reasoner is an agent published in the GitHub repository vigolium/piolium (134 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,721 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.