AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Adversarial Verify

skill-archive228-loopkit-adversarial-verify · by Archive228

Review a diff against the goal spec assuming the code is BROKEN. The reviewer

No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add skill-archive228-loopkit-adversarial-verify

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-archive228-loopkit-adversarial-verify)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Adversarial Verify? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

  1. Relaxed tests — assertions weakened or deleted to make red go green.
  2. Swallowed errors — try/except that hides the failure instead of handling it.
  3. Fake renames — a function "fixed" by renaming, behavior unchanged.
  4. Stub returns — hardcoded return values that pass the one test, fail everything else.
  5. Comment-as-fix — the bug is now a TODO.
  6. Happy-path only — 500s, empty inputs, missing files unhandled.
  7. Scope creep — changes unrelated to the goal ("while I was in there").
  8. Invented API — a method/param that doesn't exist in the actual source.
  9. Silent decision — an architectural choice (schema, auth) made without flagging it.
  10. Pass-by-mock — the test mocks the exact thing it claims to verify.
  11. 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.