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 Hawkynt/ClaudeCodePortable --skill adversarial-verifygit clone --depth 1 https://github.com/Hawkynt/ClaudeCodePortableWrote 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/hawkynt/claudecodeportable/adversarial-verify)<a href="https://agentmods.dev/skills/hawkynt/claudecodeportable/adversarial-verify"><img src="https://agentmods.dev/badge/skills/hawkynt/claudecodeportable/adversarial-verify/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/hawkynt/claudecodeportable/adversarial-verify"><img src="https://agentmods.dev/badge/skills/hawkynt/claudecodeportable/adversarial-verify.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.00082 | $0.00839 |
| Opus 5 | $0.00041 | $0.00419 |
| Sonnet 5 | $0.00016 | $0.00168 |
| Haiku 4.5 | $0.00008 | $0.00084 |
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 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.
The source is not reproduced here
Licensed LGPL-3.0
The repository is licensed LGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 38 lines · 82 tokens per session scan A bf953b2b74a8
adversarial-verify is a skill published in the GitHub repository Hawkynt/ClaudeCodePortable (2 stars, last pushed 1mo ago), licensed LGPL-3.0. It adds 82 tokens to every session and 839 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-31.
Other skills, from other repositories
pr-comments
Fetch and display GitHub PR review comments for the current branch.
chimera
Use this skill for post-session code quality review of files added or modified during a WrongStack session. It runs automatically when a session ends, and on demand. Trigger on the explicit vocabulary — "review", "code review", "quality check", "post-session review", "chimeric review", "chimera" — and on the task…
auto-review
Use this skill to configure and understand the built-in auto-review plugin (wstack-auto-review) that fires automated code review subagents on every code change during a session. Triggers: user says "auto review", "otomatik review", "auto code review", "her değişiklikte review", "/auto-review".
checkup-simplify
Use this skill when the user asks for conservative cleanup of already changed source files, similar to Claude Code /simplify, but the active agent may be Cursor, Codex, Gemini, or OpenCode.
code-review
Review frontend code for best practices, bugs, and improvements. Use when reviewing PRs, checking code quality, or before committing.
agent-computer-use
REQUIRED for any task that involves operating a desktop application — opening apps, clicking buttons, typing into fields, pressing keys, scrolling, dragging, reading what's on screen, moving or resizing windows, or verifying state after an action. Always use the agent-cu CLI commands (open, snapshot, click, type, key…