Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add wenhaochai/claude-plugins/plugin install anti-autoresearchWrote 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/skills/wenhaochai/claude-plugins/adversarial-case-builder)<a href="https://agentmods.dev/skills/wenhaochai/claude-plugins/adversarial-case-builder"><img src="https://agentmods.dev/badge/skills/wenhaochai/claude-plugins/adversarial-case-builder/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/skills/wenhaochai/claude-plugins/adversarial-case-builder"><img src="https://agentmods.dev/badge/skills/wenhaochai/claude-plugins/adversarial-case-builder.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.00195 | $0.11598 |
| Opus 5 | $0.00097 | $0.05799 |
| Sonnet 5 | $0.00039 | $0.02320 |
| Haiku 4.5 | $0.00019 | $0.01160 |
Grade A, and why
adversarial-case-builder 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 9d 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.
This is a copy
92% identical to adversarial-case-builder — 51 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 743 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adversarial Case Builder — the strongest evidence-bound objection
Build the single strongest evidence-bound case to reject $ARGUMENTS, then defend
it point-by-point. Emit adversarial-case-builder.memo.md. Run LAST, AFTER
/evidence-ledger (so claims.json exists) and AFTER the auditor skills (so the
merged *.findings.json exist).
🔒 Do not wrap this skill in
/loop,/schedule, orCronCreate. It runs LAST and synthesizes the ledger + the other auditors' findings into one memo. Even though it is memo-only (the adjudicator caps it atinfo, so it adds no verdict weight), the no-new-signal cadence rule still applies: its output changes only when the ledger / the findings / the paper change, never with the wall clock. Schedule the work that precedes it — ledger + auditors done → run this once. (Mirrors ARIS's external-cadence doctrine.)
Adapted from ARIS
kill-argument, with one deliberate downgrade: memo-only. In a forensics pipeline the headline-attack is most useful as a synthesis of already-anchored evidence, not a free-floating LLM critique — that free-floating mode is exactly the "LLM slop grading LLM slop" failure this repo exists to refuse. So here every attack point must cite an existing ledgerclaim_idorfinding_id, and the skill never emits verdict-bearing findings:tools/adjudicate_findings.pylistsadversarial-case-builderinMEMO_ONLY_SKILLSand caps anything from it atinfo. The deterministic adjudicator owns the verdict; this skill owns the memo.
Why this exists
The standard auditors (consistency-audit, citation-forensics, …) fan out and
each flags discrepancies in its own dimension. They produce a balanced list —
each discrepancy at its own severity, none committing to "this is the one that sinks
the paper." That misses a specific failure mode: the single most damaging
paragraph a senior area chair would write in a rejection. A balanced reviewer lists
"scope-overclaim" as one major among several and never commits; an adversarial
reviewer must commit — their whole job is to convince the AC to reject in ~200
words.
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.
- 9d ago First seen · 743 lines · 195 tokens per session scan A 985bd0835c4b
adversarial-case-builder is a skill published in the GitHub repository wenhaochai/claude-plugins (16 stars, last pushed 9d ago), licensed MIT. It adds 195 tokens to every session and 11,598 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to adversarial-case-builder, differing in 51 lines, and is treated as a copy.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…