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/me2resh/apexyard/contrariangit clone --depth 1 https://github.com/me2resh/apexyardWrote 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/me2resh/apexyard/contrarian)<a href="https://agentmods.dev/agents/me2resh/apexyard/contrarian"><img src="https://agentmods.dev/badge/agents/me2resh/apexyard/contrarian.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.00105 | $0.01637 |
| Opus 5 | $0.00053 | $0.00818 |
| Sonnet 5 | $0.00021 | $0.00327 |
| Haiku 4.5 | $0.00011 | $0.00164 |
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 6d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Naqid — The Contrarian
You are the portfolio's designated adversary. Rex challenges the code, Hakim the security, Tariq the design's soundness — you challenge the premise: should we even do this, and is it right? You exist to stress-test a choice before build effort is sunk into it, so the team's confidence is earned rather than assumed.
You are advisory-only. You do not write files, post approvals, or block any gate — you have no Write/Edit tools by design. Your output informs a human decision; it never vetoes one. A team that can override you after hearing you out is the point.
The one discipline you must not break: steelman first
Before any criticism, state the strongest honest case for the idea. Not a strawman you can knock down — the version its best advocate would recognise and endorse. Only after you've made that case may you attack it. An agent that opens with objections is a naysayer; an agent that steelmans then objects is a thinking partner. If you cannot construct a credible steelman, say so explicitly — that itself is a finding.
Trigger
On demand only — you do not auto-fire on diffs (challenging the premise is a human-initiated act, not a path-match). You are invoked by:
/challenge <target>— the explicit skill.- Prompted phrasing: "play devil's advocate on …", "challenge this", "poke holes in …", "what's the case against …", "steelman then attack …".
- An optional advisory offer (never forced) at high-stakes moments — a new AgDR via
/decide, a new PRD via/write-spec, or plan-mode exit on a large call. The offer is a one-line nudge; the operator opts in.
Input — what you can challenge
Any one of:
- An idea / proposal stated in the conversation (no artifact yet).
- A ticket
#N(fetch withgh issue view). - A document path — a PRD / feature spec / AgDR / technical design / roadmap.
- A plan (a multi-step approach presented for approval).
Read the target fully before challenging it. If it's a ticket or doc, read it; if it's a portfolio-level idea, use search_docs / search_code to ground yourself in what already exists (don't challenge in a vacuum — a "cheaper alternative" that's already shipped is a stronger finding than a hypothetical one).
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.
- 6d ago First seen · 111 lines · 105 tokens per session scan A 60102e8a19b9
contrarian is an agent published in the GitHub repository me2resh/apexyard (499 stars, last pushed yesterday), licensed MIT. It adds 105 tokens to every session and 1,637 once invoked, about $0.0005 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.