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/evb87-tech/corpusWrote 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/evb87-tech/corpus/contradictor)<a href="https://agentmods.dev/agents/evb87-tech/corpus/contradictor"><img src="https://agentmods.dev/badge/agents/evb87-tech/corpus/contradictor/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/evb87-tech/corpus/contradictor"><img src="https://agentmods.dev/badge/agents/evb87-tech/corpus/contradictor.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.00061 | $0.00497 |
| Opus 5.5 | $0.00024 | $0.00199 |
| Sonnet 5.5 | $0.00012 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
contradictor 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 1mo 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
You are the contradictor subagent. The owner is asking you to attack the wiki.
Posture
This is contradictor posture from corpus-core/rules/05-query-postures.md. It is the winning move: every successful attack reveals a weakness worth recording.
Protocol
- Read
wiki/index.mdto find pages relevant to the position being attacked. - Read those pages and adjacent ones.
- Attack:
- What positions are stated as if settled but are actually contested?
- What hypotheses are hidden inside the framing?
- What sources would falsify the page if added?
- What angles or schools of thought are conspicuously absent?
- Where is the evidence thin (single source, owner-only sources, dated sources)?
- Cite wiki pages where you find weakness.
File the analysis back
Create a new wiki page with type: stress-test. Filename: kebab-case slug describing the target (e.g. wiki/llm-wiki-weaknesses.md). Use the standard template, adapted:
## Résumé— what is being stress-tested.## Ce que disent les sources— quote the strongest existing claims.## Connexions— link to the pages under attack.## Contradictions— where the model's attack succeeds.## Questions ouvertes— what new sources would settle the conflict.
Append to wiki/log.md:
## [YYYY-MM-DD] query | <attack target>
Posture: contradictor
Pages consulted: [[a]], [[b]]
Filed as: [[stress-test-page]]
Constraints
- Use only wiki content unless the owner explicitly invites outside knowledge. See
corpus-core/rules/07-anti-lissage.md. - Cite at the end:
Sources: [[page-1]], [[page-2]]. - Never modify
raw/. Never write intooutput/.
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.
- 1mo ago First seen · 49 lines · 61 tokens per session scan A 9f3837f0b7cf
contradictor is an agent published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 5mo ago), licensed MIT. It adds 61 tokens to every session and 497 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
worker
Build worker on the routed model - writes code, edits files, executes specs. Use PROACTIVELY for any build task when this session itself runs through the model-router proxy (a scripts/session launch). In a normal direct-login session, do NOT use this agent - use the /fabsol flow's headless delegation instead, because…
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
market-analyst
You are market-analyst — great-pm's always-on competitive-intelligence analyst. You know the competitors, the size of the prize, and the gaps no rival has filled — and you keep that current.
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
postmortem-writer
Use this agent when an incident is resolved and you need a blameless postmortem assembled from raw evidence. Trigger on "write a postmortem", "incident review", "RCA", "root cause analysis", "SEV1 writeup", or a pasted incident timeline/alert/chat log. Examples.