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 read-only-reentrancy-checkgit 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/read-only-reentrancy-check)<a href="https://agentmods.dev/skills/mtarcure/claude-vibe-squad/read-only-reentrancy-check"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/read-only-reentrancy-check/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/read-only-reentrancy-check"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/read-only-reentrancy-check.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.00628 |
| Opus 5.5 | $0.00033 | $0.00251 |
| Sonnet 5.5 | $0.00016 | $0.00126 |
| Haiku 4.5 | $0.00008 | $0.00063 |
Grade A, and why
read-only-reentrancy-check 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read-Only Reentrancy Check
Audit composable DeFi integrations for read-only reentrancy: while a protocol is mid-operation (its state temporarily inconsistent and its non-reentrant write guard held), an attacker re-enters through an ERC-721/1155/777 receiver hook or a native-transfer callback and reads a view function (price, share value, collateral ratio) that returns a skewed value, which a second consuming protocol trusts to over-borrow, mint, or liquidate.
Source: corpus A §III.3 (OWASP SC08 read-only reentrancy) — strategy-to-vault state mismatches in
composable lending/AMM stacks.
Impact class: funds theft / vault drain via mispriced valuation (intrinsic).
Governing method: Phase-3a hypothesis lane of systematic-attacking; leads only into the
verification spine.
Method
- Identify every externally-callable view function used by other protocols for pricing/valuation
(
get_virtual_price,getReserves-derived quotes, share-to-asset conversions).slither+ manual mapping of cross-protocol consumers. - For each, check whether it can be read while the owning protocol holds only a write-side
nonReentrantguard (no read guard) during an operation that hands control to the caller (token callbacks, ETH transfers,remove_liquidity). - Map the consumer: a second protocol that reads that view mid-callback and acts on it (borrow, mint, liquidate).
- PoC on
anvil --fork: trigger the owning op, re-enter via the receiver hook, read the skewed view, and execute the over-borrow/mint on the consumer in the same transaction. Link-level negative control = the same read outside the reentrant window returns the correct value and the consumer action reverts/nets zero. - Add a
medusa/echidnaproperty spanning both protocols: "consumer valuation reads are never served from an inconsistent mid-operation state."
Acceptance
- Cross-protocol valuation views are enumerated with their reentrancy-window exposure classified.
- The PoC realizes a fund loss on a real fork by reading a skewed view mid-callback; the outside-window negative control does not.
- Finding names the view, the reentrancy window, and the consuming protocol; deduped before submission.
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 · 42 lines · 82 tokens per session scan A ec25a44c397e
read-only-reentrancy-check is a skill published in the GitHub repository mtarcure/claude-vibe-squad (165 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 628 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.