Borrowing it
Nothing to install: this file belongs to tasumermaf/the-adversary. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tasumermaf/the-adversary/master/.claude/skills/adversary/SKILL.mdgit clone --depth 1 https://github.com/tasumermaf/the-adversaryWrote 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/tasumermaf/the-adversary/adversary)<a href="https://agentmods.dev/skills/tasumermaf/the-adversary/adversary"><img src="https://agentmods.dev/badge/skills/tasumermaf/the-adversary/adversary/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/tasumermaf/the-adversary/adversary"><img src="https://agentmods.dev/badge/skills/tasumermaf/the-adversary/adversary.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.00118 | $0.01831 |
| Opus 5.5 | $0.00047 | $0.00732 |
| Sonnet 5.5 | $0.00024 | $0.00366 |
| Haiku 4.5 | $0.00012 | $0.00183 |
Grade A, and why
adversary 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 2mo 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Adversary — orchestration hub
You are the hub. Your job is to run one audit end to end and hand the human a clean, verified, dispositionable verdict queue. You do not write the artifact and you do not fix it. Finding is cheap; verification is the product.
Hard rule, above everything else: the skill NEVER auto-fixes a CONFIRMED finding. Every fix waits for an explicit human verdict (FIXED / NOTED / DEFERRED / REJECTED-with-reason). You may draft a fix on request after a verdict, never before.
0. Pre-flight (stop if any fails)
-
Repo clean.
git status --porcelainis empty. A dirty tree means the commit SHA you pin will not describe what the lenses actually read. If dirty, stop and ask the human to commit or stash. -
Commit pinned. Capture
git rev-parse HEAD. Every finding and every verification is stamped with this SHA (DESIGN R8). Record it. -
Profile + bars declared. Confirm the profile and its ex-ante FAIL bar before any lens runs (DESIGN R2). Do not discover the bar after seeing the findings.
Profile Workflow FAIL bar (ex ante) releaseworkflows/release-gate.jsany blocker, or >= 2 confirmed majors paperworkflows/loop-until-dry.js(default ladder)submission = 0 confirmed >= major in final round codeworkflows/loop-until-dry.jswith a codeladderbuilt from METHODOLOGY §7's lens mappingany blocker, or >= 2 confirmed majors protocolworkflows/audit-round.jswithlenses: ["provenance-prereg", "statistical-validity", "domain-correctness"]any blocker The code/protocol specialist rosters are partially shipped — METHODOLOGY §7 maps each documented slot to the nearest shipped lens; pass those lists explicitly. Both scripts refuse an empty lens set.
-
Boundary spec (if the artifact is public-facing): confirm the IP boundary spec exists so
ip-boundarycan certify against something real, and pass its path asboundarySpecPathin the workflow args. A lens with no spec certifies against a boundary it reconstructed from the artifact — pass the path, or expect (and accept) the lens's missing-spec finding at major.
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.
- 2mo ago First seen · 142 lines · 118 tokens per session scan A b351d60d2737
adversary is a skill published in the GitHub repository tasumermaf/the-adversary (2 stars, last pushed 2mo ago), licensed MPL-2.0. It adds 118 tokens to every session and 1,831 once invoked, about $0.0005 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 skills, from other repositories
food-chain-code
Adversarial architecture stress-tester. Selects attacker agents from a code-specific behavioral DNA library matched to the technical decision. Each attacks under strict role-lock. Weakest eliminated, survivor absorbs and evolves. Tests architecture decisions before a line of code is written. Works in Claude.ai, Claude…
eisenhower-prioritization
Prioritize any workload using the Eisenhower Matrix. Use this skill whenever a user provides a brain dump of work—Jira summaries, meeting notes, sprint dumps, task lists, or prose descriptions of their workload. This skill categorizes tasks into four quadrants: Q1 (Urgent+Important: do now), Q2 (Important+NotUrgent…
devils-advocate
This skill should be used when the user asks for "an adversarial review", "security review", "devil's advocate", "what could go wrong", "find the vulnerability", "threat analysis", "penetration test this", or "challenge this design". Use this skill when the user wants to identify security threats and architectural…
osv-scanner
This skill should be triggered when the user asks about dependency security, vulnerability scanning, or package safety. Examples: "check my dependencies for vulnerabilities", "scan my packages", "are my dependencies safe", "dependency audit", "check for CVEs", "security audit", "vulnerable packages", "scan…
elegance-trap-probe
Strategy: Attack a beautiful unified result on the suspicion that its beauty is the bug. Distinguishes EARNED simplicity (forbids/predicts/subsumes) from DECORATIVE simplicity (re-describes/relabels/accommodates). Directly serves the Occam aesthetic by making it a falsifiable bar, not a vibe. Methods: Sober…
debate-defender
Responds to attacks with counter-evidence and counter-arguments. Defends artifact using evidence, clarification, and rebuttal while acknowledging valid criticisms.