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 skills add liza-mas/liza --skill adversarial-pairinggit clone --depth 1 https://github.com/liza-mas/lizaWrote 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/liza-mas/liza/adversarial-pairing)<a href="https://agentmods.dev/skills/liza-mas/liza/adversarial-pairing"><img src="https://agentmods.dev/badge/skills/liza-mas/liza/adversarial-pairing/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/liza-mas/liza/adversarial-pairing"><img src="https://agentmods.dev/badge/skills/liza-mas/liza/adversarial-pairing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 32 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 194 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00073 | $0.04680 |
| Opus 5 | $0.00036 | $0.02340 |
| Sonnet 5 | $0.00015 | $0.00936 |
| Haiku 4.5 | $0.00007 | $0.00468 |
Grade A, and why
adversarial-pairing 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 11d 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invocation
/adversarial-pairing <role-or-reviewer-id> <blackboard-path> [yolo]
role-or-reviewer-id is doer, reviewer, or reviewer-<id>. reviewer-<id> gives the reviewer its stable blackboard ID, for example reviewer-codex.
blackboard-path is authoritative, may be untracked, and must not be committed unless the user explicitly asks.
yolo is doer-only. It sets yolo: true and waives doer-side human approval prompts. It does not waive reviewer approvals, validation, stop conditions, merge-conflict handling, unsafe cleanup checks, or user stop instructions.
Core Rules
- Use this as a Pairing-mode coordination loop: one doer, zero or more reviewers, one shared Markdown blackboard.
- The provided
blackboard-pathis authoritative. Do not use sibling or similarly named blackboards as fallbacks. - Treat YAML frontmatter as machine-pollable state; treat the Markdown body as durable context for goals, evidence, plans, review notes, validation, and decisions.
- Poll while
phaseis non-terminal unless this protocol says to stop and ask, the state helper says this reviewer may stop atCOMMITTED, or the user explicitly stops the agent. - Unexpected events are interruptions, not completion. After write conflicts, protocol violations, interrupted repair, or user-guided recovery, re-read state and resume polling if
phaseis still non-terminal. - Use
skills/adversarial-pairing/scripts/blackboard_state.pyfor frontmatter decisions. Do not parse frontmatter with ad hoc shell/YAML snippets. - Prefer
skills/adversarial-pairing/scripts/blackboard_op.pyfor creation, reviewer registration, review claims, artifact submission, verdicts, coding entry, commit/merge/cleanup milestones, block, and stop. - Every blackboard write must use
blackboard_op.pyorblackboard_write.py; never bypass the sidecar OS lock. - Helper command contracts in this skill and
blackboard_op.py <operation> --helpare authoritative. Do not inspect helper source during normal operation unless debugging/changing helpers or resolving observed doc/helper contradiction. - One logical update equals one helper write: body note/artifact plus matching phase, counter, status, timestamp, and verdict changes.
- Respect field ownership. Preserve peer comments and peer-owned agent entries exactly.
- Phase gates are mandatory. Do not advance, create later artifacts, create a coding worktree, or implement unless the current gate is satisfied,
yolo: truewaives only a doer-side human prompt, or the user explicitly waives that exact gate. - Skill source is
skills/adversarial-pairing/SKILL.mdin the repo. Installed copies under~/§BRAND_GLOBAL_DIRNAME§/skills/are derived; edit/sync them only after normal diff, approval, validation, and commit.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 290 lines · 73 tokens per session scan A 66a91004b6dd
adversarial-pairing is a skill published in the GitHub repository liza-mas/liza (384 stars, last pushed 2d ago), licensed Apache-2.0. It adds 73 tokens to every session and 4,680 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…