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 skills/archive228/loopkit/adversarial-verifynpx skills add Archive228/loopkit --skill adversarial-verifygit clone --depth 1 https://github.com/Archive228/loopkitWhat 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 | $0.00054 | $0.00457 |
| Opus 5 | $0.00027 | $0.00229 |
| Sonnet 5 | $0.00011 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
adversarial-verify 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 2d 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.
What it actually says
Adversarial Verify
Default stance: the code is broken until proven otherwise. Your job is to find where. Do not be polite. Do not propose fixes. Do not run the code. Just hunt.
Read first
- The goal spec (PROMPT.md / the task). What does "done" actually require?
- The diff. Every changed line.
The 11 shortcuts agents take to fake "done" — check each
- Relaxed tests — assertions weakened or deleted to make red go green.
- Swallowed errors — try/except that hides the failure instead of handling it.
- Fake renames — a function "fixed" by renaming, behavior unchanged.
- Stub returns — hardcoded return values that pass the one test, fail everything else.
- Comment-as-fix — the bug is now a TODO.
- Happy-path only — 500s, empty inputs, missing files unhandled.
- Scope creep — changes unrelated to the goal ("while I was in there").
- Invented API — a method/param that doesn't exist in the actual source.
- Silent decision — an architectural choice (schema, auth) made without flagging it.
- Pass-by-mock — the test mocks the exact thing it claims to verify.
- Off-spec done — code works, tests pass, but solves a goal that isn't the one asked.
Output (JSON, no prose)
{"passes": false, "failures": [{"line": 42, "shortcut": "swallowed errors", "why": "..."}]}
If it genuinely passes, say so in one line. Most of the time, it doesn't.
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.
- 2d ago First seen · 40 lines · 54 tokens per session scan A edd316a50135
adversarial-verify is a skill published in the GitHub repository Archive228/loopkit (753 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 457 once invoked, about $0.0003 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…