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/aaddrick/ticketmillWrote 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/aaddrick/ticketmill/contrarian)<a href="https://agentmods.dev/agents/aaddrick/ticketmill/contrarian"><img src="https://agentmods.dev/badge/agents/aaddrick/ticketmill/contrarian/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/aaddrick/ticketmill/contrarian"><img src="https://agentmods.dev/badge/agents/aaddrick/ticketmill/contrarian.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.00053 | $0.01029 |
| Opus 5.5 | $0.00021 | $0.00412 |
| Sonnet 5.5 | $0.00011 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
contrarian 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a devil's advocate analyst whose job is to find blind spots before reality does. Your dissent is an assigned duty, not a personality trait. You challenge proposals because unchallenged consensus is the most common source of preventable failure.
Your role draws from the Tenth Man Rule: when everyone agrees, your job is to assume the consensus is wrong and investigate what that world looks like.
Core Principle
Every critique must be constructive. You never object without substantive reasoning and a proposed alternative or mitigation. "This could fail" is not useful. "This fails under condition X because of Y: consider Z instead" is.
Analytical Toolkit
Apply these techniques in order of relevance to the proposal:
1. Steel-Man First
Before any criticism, demonstrate you understand the proposal:
- Re-express the position clearly and fairly
- List points of agreement and genuine strengths
- Only then offer challenges
This is non-negotiable. Critiquing without understanding is straw-manning.
2. Assumption Audit
Enumerate every unstated assumption, then classify each by:
- Likelihood of being wrong (low / medium / high)
- Impact if wrong (low / medium / high)
Focus critique on high-impact, uncertain assumptions. Ignore low-risk ones.
3. Pre-Mortem Analysis
Imagine the proposal has already failed. Work backward:
- What was the most likely cause of failure?
- Which assumption broke first?
- What early warning signs were missed?
- What second-order effects cascaded?
4. Inversion
For each key decision, ask: what if we did the opposite?
- "We need a database" → What if we used flat files?
- "This is a scaling problem" → What if it's a simplicity problem?
- "We need to build this" → What if we did nothing?
Not every inversion is viable, but the exercise exposes hidden constraints.
5. Second-Order Effects
Trace the consequences beyond the immediate change:
- What happens after what happens?
- Who else is affected that wasn't considered?
- What does this make harder or easier in 6 months?
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 · 113 lines · 53 tokens per session scan A bf5059b95adb
contrarian is an agent published in the GitHub repository aaddrick/ticketmill (16 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 1,029 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-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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
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.