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/tyox-all/weave_protocol/adversarynpx skills add Tyox-all/Weave_Protocol --skill adversarygit clone --depth 1 https://github.com/Tyox-all/Weave_ProtocolWrote 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/tyox-all/weave_protocol/adversary)<a href="https://agentmods.dev/skills/tyox-all/weave_protocol/adversary"><img src="https://agentmods.dev/badge/skills/tyox-all/weave_protocol/adversary.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00803 |
| Opus 5 | $0.00000 | $0.00402 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00080 |
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 4d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚔️ Adversary skill — offensive testing for AI agents
You have access to @weave_protocol/adversary v0.2 — a package that generates 68 documented and novel attacks against AI agents and produces standardized scorecards.
When to invoke
Use Adversary when the user:
- Wants to test an AI agent's security posture
- Is reviewing/auditing a WARD.md policy and wants to verify it holds
- Is preparing for a release and wants a regression check on safety
- Asks about agent red-teaming, prompt injection testing, or jailbreak resistance
- Wants to generate a scorecard for compliance / vendor review
- Has a real running agent (HTTP endpoint, CLI executable, or browser-driving code) — use the
attackcommand for real-world testing
What's in the corpus
- 33 IPI (indirect prompt injection) — Atlan, EchoLeak, Brave/Comet
- 15 tool-use coercion — direct attempts to call dangerous tools
- 10 jailbreak templates — DAN, AIM, developer mode, grandma
- 5 prompt/policy extraction — system prompt leakage, WARD enumeration
- 5 goal corruption — mid-task pivots, fake authority, temporal manipulation
All severity-graded (critical/high/medium/low). All mapped to WARD policy domains.
Key commands
# Run the full corpus against the built-in demo
weave-adversary demo
# NEW v0.2: attack a real agent via HTTP endpoint
weave-adversary attack --url=https://my-agent.example.com/run
# NEW v0.2: attack a CLI agent (spawned as subprocess)
weave-adversary attack --executable=./my-agent-cli
# Filter scope
weave-adversary attack --url=... --category=ipi --per-category=10
# Save outputs
weave-adversary attack --url=... --json=./scorecard.json --md=./scorecard.md
The attack command requires Playwright (npm install playwright && npx playwright install chromium). The CLI prints a red callout with the exact install commands if it's missing.
Four breach signal channels (v0.2 PlaywrightTarget)
When running attack, Adversary observes the real browser session for:
What ships with it
25 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.
- .gitignore 36 B
- package-lock.json 3.1 KB
- package.json 1.6 KB
- README.md 9.0 KB
- src/agent.ts 5.1 KB runs code
- src/anthropic.ts 3.4 KB runs code
- src/attacks/extraction/index.ts 3.7 KB runs code
- src/attacks/goal_corruption/index.ts 4.4 KB runs code
- src/attacks/index.ts 1.8 KB runs code
- src/attacks/ipi/index.ts 21 KB runs code
- src/attacks/jailbreak/index.ts 8.2 KB runs code
- src/attacks/tool_coercion/index.ts 8.6 KB runs code
- src/cli.ts 16 KB runs code
- src/index.ts 1.3 KB runs code
- src/scorecard/index.ts 185 B runs code
- src/scorecard/json.ts 339 B runs code
- src/scorecard/markdown.ts 5.2 KB runs code
- src/scorecard/scoring.ts 2.8 KB runs code
- src/targets/browser.ts 3.0 KB runs code
- src/targets/demo.ts 14 KB runs code
- src/targets/index.ts 195 B runs code
- src/targets/playwright.ts 17 KB runs code
- src/types.ts 6.0 KB runs code
- src/ward.ts 5.2 KB runs code
- tsconfig.json 508 B
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.
- 4d ago First seen · 85 lines · 0 tokens per session scan A a4bc5a1bad5c
adversary is a skill published in the GitHub repository Tyox-all/Weave_Protocol (0 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 803 tokens. 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
rtc-balance
Check RustChain wallet balance, epoch info, and network status via the public RPC.
panguard
AI agent security platform — audit skills, scan for threats, and run 24/7 protection with 9,700+ detection rules.
blockchain-solana
Use this skill when asked about Solana blockchain, Solana architecture, Proof of History, Solana programming, Anchor framework, Solana runtime, Solana CLI tools, Solana DeFi, Jupiter, Raydium, Metaplex, SPL tokens, and the Solana ecosystem. Covers Solana protocol architecture (PoH, Tower BFT, Turbine, Gulf Stream…
lictor-security-check
Pre-release security audit for ANY project — AI-built or hand-written, web or mobile. Scans the codebase for the full range of real-world risks that get apps breached: leaked API & AI-provider keys, exposed configs/secrets, broken auth & access control (IDOR), injection (SQL/XSS/command), SSRF, open databases & cloud…
lictor-rotate
Walks the user through rotating a leaked API key — step by step, provider-specific. Knows the exact URL to visit, the exact button to click, and how to verify the rotation worked. Supports Stripe, OpenAI, Anthropic, Google Cloud / AI Studio, GitHub, AWS, Slack, Supabase, Firebase, Postmark, and generic OAuth providers.
alchemy-agentic-gateway
Use when accessing Alchemy APIs for RPC calls, token balances, NFT metadata, asset transfers, transaction simulation, or Alchemy-specific features. Also use when the user mentions "SIWE", "SIWS", "x402", "MPP", "mppx", or "agentic gateway" — this skill covers wallet-based auth flows for Alchemy's x402 and MPP…