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 mtarcure/claude-vibe-squad --skill durable-nonce-exploitationgit clone --depth 1 https://github.com/mtarcure/claude-vibe-squadWrote 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/mtarcure/claude-vibe-squad/durable-nonce-exploitation)<a href="https://agentmods.dev/skills/mtarcure/claude-vibe-squad/durable-nonce-exploitation"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/durable-nonce-exploitation/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/mtarcure/claude-vibe-squad/durable-nonce-exploitation"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/durable-nonce-exploitation.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.00083 | $0.01056 |
| Opus 5.5 | $0.00033 | $0.00422 |
| Sonnet 5.5 | $0.00017 | $0.00211 |
| Haiku 4.5 | $0.00008 | $0.00106 |
Grade A, and why
durable-nonce-exploitation 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 1mo 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solana Durable-Nonce Exploitation Audit
Audit a Solana governance, multisig, or administrative approval workflow for a narrow time-shift primitive: an unprivileged actor causes the required authorities to sign the actor's exact durable-nonce transaction without reliably seeing its true intent, then holds that still-valid authorization until a later first submission reaches an unauthorized state or funds terminus.
Durable validity is not itself a vulnerability. A transaction that was signed, never submitted, and later lands is normal protocol behavior; do not call it replay. Successful first execution consumes the nonce value, so repeated submission of the same transaction is not the primitive.
Impact class: privileged/control-plane takeover, unauthorized state transition, or funds moved
without the attacker's prior privilege.
Governing method: Phase-3a hypothesis lane of systematic-attacking; keep the result as a lead
until the verification spine promotes it. Any live-target signing or submission is operator-gated.
Precondition gate
Before building a delayed-submission harness, prove all of these on the target workflow:
- Start from an unprivileged actor. Identify the real proposer, coordinator, UI, encoder, or message replacement path by which that actor can choose or alter the exact serialized transaction that authorities sign.
- Enumerate every required signature, including the durable-nonce authority and each authority for the terminal instruction. Show how the ordinary target workflow yields those signatures over the attacker-selected message without stolen credentials, compromised keys, privileged collusion, or a signer deliberately authorizing the disclosed action.
- Bind the display to the signed bytes. Record what each signer sees and prove the approval surface can misdescribe, omit, or fail to authenticate a security-relevant instruction in the exact message. An opaque signature alone is not proof that an attacker can obtain it.
- Show that the actor can retain and submit the fully signed transaction while its recorded nonce value remains current. Control of a nonce account alone is insufficient unless it establishes the required signature or submission precondition.
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.
- 1mo ago First seen · 83 lines · 83 tokens per session scan A 92cfe5bcb0e0
durable-nonce-exploitation is a skill published in the GitHub repository mtarcure/claude-vibe-squad (165 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 1,056 once invoked, about $0.0003 per session on Opus 5.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-09-19.
Other skills, from other repositories
pay
Pay one external payment requirement within exact parent authority, through a payment method the payer holds, and read the paid resource back.
aomi-transact
Build natural-language crypto/DeFi agents and EVM MCP plugins (Claude Code, Cursor, Codex, Gemini). Aomi turns prompts into wallet-signed txs on Ethereum, Base, Arbitrum, Optimism, Polygon, Linea — non-custodial, fork-simulated. 40+ apps: Uniswap, Aave, Lido, Morpho, GMX, Hyperliquid, Polymarket.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
document
Skill "document" from Hmbown/Codewhale, covering document, when to use, non-goals and workflow.