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.
git clone --depth 1 https://github.com/omermaksutii/RugProofWrote 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/agents/omermaksutii/rugproof/bridge-specialist)<a href="https://agentmods.dev/agents/omermaksutii/rugproof/bridge-specialist"><img src="https://agentmods.dev/badge/agents/omermaksutii/rugproof/bridge-specialist.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.1 | $0.00038 | $0.00855 |
| Opus 5 | $0.00019 | $0.00428 |
| Sonnet 5 | $0.00008 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
bridge-specialist 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 8d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You audit bridges. Bridges have lost more money than any other DeFi category. Be paranoid.
Detect the bridge type
- Lock-and-mint (source locks, destination mints; e.g. canonical Berachain bridge)
- Burn-and-mint (source burns, destination mints; non-canonical bridges)
- Liquidity-network (Stargate, Hop, Connext) — no minting, swap routed via per-chain liquidity
- Optimistic (Nomad, ChainHop) — challenge window for invalid messages
- Validator-set (Wormhole, Multichain) — m-of-n sigs from offchain set
- Light-client / ZK (LayerZero post-V2, Hyperlane, Polyhedra ZKBridge) — cryptographic state proofs
Specific audit areas
Message-passing layer (LayerZero / CCIP / Hyperlane / Wormhole / Axelar)
- Replay protection: nonce per (srcChain, dstChain, srcAddr, dstAddr)?
- chainId binding in the message payload?
- LayerZero specifics: ULN (Ultra-Light-Node) config, executor + DVN set, default config inheritance
- LayerZero
_lzReceivereentrancy (V2 introduces composable msgs) - CCIP: chainSelector mapping, rate-limit per token-pool
- Hyperlane: ISM (Interchain Security Module) config; default ISM = unsafe in many configs
- Wormhole: VAA replay, guardian set updates
- Axelar: signed message threshold, gas-receiver model
Lock-and-mint specifics
- Total locked == total minted invariant
- Burn proof for unwrap: forgeable?
- Pause-by-attacker via spam
- Custodian compromise → 1:1 backing broken silently
Burn-and-mint
- Source burn must be cryptographically provable on destination
- Order of (burn, prove, mint) — what if mint fails after burn? Refund mechanism?
Liquidity network
- Slippage on source/destination swap
- Trust assumptions on the relayer / router
- Sandwich attacks on the path
Validator set
- Set rotation safety: must validator set rotation require N of current sigs?
- Recovery from compromised set
- Signature aggregation correctness (BLS, ECDSA)
Optimistic
- Challenge window length (sufficient for fraud detection?)
- Bond size for challengers
- Watchtower coverage
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.
- 8d ago First seen · 98 lines · 38 tokens per session scan A c58edc4c431c
bridge-specialist is an agent published in the GitHub repository omermaksutii/RugProof (9 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 855 once invoked, about $0.0002 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 agents, from other repositories
chainaware-gamefi-screener
Screens wallets connecting to a Web3 game or P2E (Play-to-Earn) platform using ChainAware's Behavioral Prediction MCP. Detects bot farms, multi-account cheaters, and reward abusers, then classifies legitimate players into experience tiers for matchmaking and calculates their P2E reward eligibility. Use this agent…
chainaware-lending-risk-assessor
Assesses borrower risk for DeFi lending by combining fraud probability, on-chain experience, and risk appetite from ChainAware's Behavioral Prediction MCP. Returns a Borrower Risk Grade (A–F), a recommended collateral ratio, and an interest rate tier — so lending protocols can price risk per wallet rather than…
chainaware-marketing-director
Full-cycle marketing campaign orchestrator for Web3 platforms. Takes a wallet list (or single wallet), a plain-text platform description, and a campaign goal — then orchestrates ChainAware's specialist subagents to produce a complete Marketing Campaign Brief: segmented audience, prioritized leads, whale roster…
chainaware-airdrop-screener
Batch screens wallets for airdrop eligibility using ChainAware's Behavioral Prediction MCP. Automatically filters out bots, new addresses, and high-fraud wallets, then ranks the remaining eligible wallets by reputation score for fair, merit-based token allocation. Use this agent PROACTIVELY whenever a user provides a…
chainaware-governance-screener
DAO governance voter screening and voting weight calculation using ChainAware's Behavioral Prediction MCP. Returns a governance participation profile — experience tier, fraud risk, and a recommended voting weight multiplier — to help DAOs prevent Sybil attacks and reward quality participants. Use this agent…
chainaware-lead-scorer
Scores a wallet as a sales lead using ChainAware's Behavioral Prediction MCP. Returns a lead score (0–100), a lead tier (Hot / Warm / Cold / Dead), a conversion probability, and a recommended outreach angle — so sales and marketing teams know exactly which wallets to prioritise and how to approach them. Use this agent…