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 instructions/persistenceone/bridgekitty/claude-mdgit clone --depth 1 https://github.com/persistenceOne/bridgekittyWhat 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.01713 | $0.01713 |
| Opus 5 | $0.00856 | $0.00856 |
| Sonnet 5 | $0.00343 | $0.00343 |
| Haiku 4.5 | $0.00171 | $0.00171 |
Grade A, and why
bridgekitty CLAUDE.md 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 yesterday.
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — BridgeKitty Project Context
What is this?
BridgeKitty is a cross-chain bridge aggregator MCP server for AI agents. It gives Claude, GPT, Cursor, or any MCP-compatible AI the ability to find and execute cross-chain bridge transfers. Think "1inch for bridges, but the user is an AI agent."
One MCP server → 6 bridge backends → best routes across EVM, Cosmos, and Solana chains.
The hook: any-to-any bridging for agents across all major ecosystems. The sticky feature: XPRT farming rewards (earn XPRT by bridging BTC variants via Persistence Interop).
Architecture
src/
├── index.ts # Entry point — MCP server setup, backend init
├── routing/engine.ts # Multi-backend routing engine (parallel quotes, ranking)
├── backends/ # Bridge provider integrations
│ ├── types.ts # Shared interfaces (BridgeQuote, TransactionRequest, etc.)
│ ├── lifi.ts # LI.FI aggregator (30+ bridges, widest coverage)
│ ├── squid.ts # Squid Router (cross-ecosystem: EVM ↔ Cosmos ↔ Solana)
│ ├── debridge.ts # deBridge DLN (fast intents, Solana support)
│ ├── across.ts # Across (fastest fills ~6s)
│ ├── relay.ts # Relay (gas-optimized)
│ └── persistence.ts # Persistence Interop (BTCB↔cbBTC, XPRT rewards)
├── tools/ # MCP tool definitions (what the AI agent calls)
│ ├── get-quote.ts # bridge_get_quote — multi-backend quote comparison
│ ├── execute-bridge.ts # bridge_execute — returns unsigned tx data
│ ├── check-status.ts # bridge_status — track bridge progress
│ ├── get-chains.ts # bridge_chains — list supported chains
│ ├── get-tokens.ts # bridge_tokens — list tokens per chain
│ ├── multi-quote.ts # bridge_quote_multi — multi-hop route resolution
│ ├── help.ts # bridgekitty_help — agent onboarding guide
│ ├── xprt-rewards.ts # xprt_rewards_check — reward accrual visibility
│ ├── onboard.ts # xprt_onboard — guided onboarding flow
│ ├── wallet.ts # wallet_setup + wallet_balance (with USD valuations)
│ └── xprt-farm.ts # xprt_farm_* (prepare/start/status/boost with dry-run)
└── utils/ # Shared utilities
├── token-registry.ts # Curated verified token addresses (anti-phishing)
├── chains.ts # Chain ID → name/RPC mapping
├── circuit-breaker.ts # Per-backend circuit breaker
├── gas-estimator.ts # Gas cost estimation in USD (multi-RPC failover)
├── evm.ts # ERC20 approve helpers
├── tokens.ts # Token amount formatting
├── tx-simulator.ts # eth_estimateGas pre-flight checks
└── sanitize-error.ts # Strip sensitive info from errors
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.
- yesterday First seen · 117 lines · 1,713 tokens per session scan A 6f3aebb5f3b5
bridgekitty CLAUDE.md is an instructions file published in the GitHub repository persistenceOne/bridgekitty (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,713 tokens to every session, about $0.0086 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.