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/nirholas/three.ws/tool-registry-guidenpx skills add nirholas/three.ws --skill tool-registry-guidegit clone --depth 1 https://github.com/nirholas/three.wsWrote 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/nirholas/three.ws/tool-registry-guide)<a href="https://agentmods.dev/skills/nirholas/three.ws/tool-registry-guide"><img src="https://agentmods.dev/badge/skills/nirholas/three.ws/tool-registry-guide.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.00066 | $0.01140 |
| Opus 5 | $0.00033 | $0.00570 |
| Sonnet 5 | $0.00013 | $0.00228 |
| Haiku 4.5 | $0.00007 | $0.00114 |
Grade A, and why
tool-registry-guide scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://registry.lyra.tools/api/search?q=stablecoin How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lyra Tool Registry Guide
Lyra Registry is a standalone API + MCP service that catalogs, scores, and serves metadata for 800+ crypto and DeFi tools. It's the discovery layer for the Sperax/Lyra ecosystem.
What's in the Registry
| Category | Count | Examples |
|---|---|---|
| DeFi Protocols | 200+ | Aave, Compound, Uniswap, Sperax |
| Market Data | 100+ | CoinGecko, DeFi Llama, DexScreener |
| Trading Bots | 80+ | Grid bots, DCA tools, arbitrage |
| Wallet Tools | 60+ | Validators, generators, managers |
| NFT Tools | 50+ | Marketplaces, analytics, minting |
| Security | 40+ | Audit tools, honeypot detection |
| Bridge/Cross-Chain | 50+ | Across, Stargate, Wormhole |
| MCP Servers | 100+ | All registered MCP servers |
| Other | 120+ | Governance, education, analytics |
API Endpoints
Search Tools
# Search by keyword
curl https://registry.lyra.tools/api/search?q=stablecoin
# Filter by category
curl https://registry.lyra.tools/api/tools?category=defi&chain=arbitrum
# Get trending tools
curl https://registry.lyra.tools/api/trending
# Get tool details
curl https://registry.lyra.tools/api/tools/sperax-usds
Tool Scoring
Every tool has a quality score based on:
| Factor | Weight | Description |
|---|---|---|
| Documentation | 20% | README quality, guides, API docs |
| Maintenance | 20% | Recent commits, issue response time |
| Community | 15% | Stars, forks, contributors |
| Security | 20% | Audits, dependencies, practices |
| Functionality | 15% | Feature completeness, reliability |
| Compatibility | 10% | MCP support, standard compliance |
Example Score
{
"name": "sperax-crypto-mcp",
"score": 0.92,
"breakdown": {
"documentation": 0.95,
"maintenance": 0.90,
"community": 0.85,
"security": 0.95,
"functionality": 0.93,
"compatibility": 0.98
}
}
MCP Server
The registry itself is an MCP server:
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 · 138 lines · 66 tokens per session scan A 2fd1663bf934
tool-registry-guide is a skill published in the GitHub repository nirholas/three.ws (110 stars, last pushed today), licensed Apache-2.0. It adds 66 tokens to every session and 1,140 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
blockchain-cross-chain
Cross-chain protocols, IBC, LayerZero, Wormhole, Axelar, CCIP, bridges, atomic composability, shared sequencer, cross-chain message passing. Covers trust models (light clients, external validators, ZK proofs), bridge security, token representation (canonical, wrapped, native), relayer economics, and cross-chain…
blockchain-security
Use this skill when asked about blockchain security, smart contract auditing, DeFi threat modeling, blockchain incident response, bug bounty programs, economic security, formal verification of smart contracts, and blockchain-specific security analysis. Languages: Solidity, Python, Rust, Haskell. Covers threat modeling…
blockchain-testing
Use this skill when asked about testing smart contracts, Foundry tests, Hardhat tests, fuzz testing, invariant testing, property-based testing, formal verification, audit preparation, integration testing for dApps, and blockchain testing patterns. Covers Foundry cheatcodes, Echidna fuzzing, Certora verification…
xpr-network-dev
XPR Network (formerly Proton) blockchain development - proton-tsc smart contracts, @proton CLI and web SDK, RPC and Hyperion queries, DeFi (MetalX, Alcor, LOAN), NFTs, the XPR Agents job board, node and Hyperion operations. Use for anything mentioning XPR, Proton, or @proton packages.
blockchain-management
Use this skill when asked about blockchain project management, DAO governance, multi-sig operations, treasury management, tokenomics design, and web3 project methodology. Languages: Solidity, TypeScript, Python. Covers DAO governance frameworks (Compound Governor, Aave, Snapshot, Tally), multi-sig wallet operations…
modernize-move
Detects and modernizes outdated Move V1 syntax, patterns, and APIs to Move V2+. Use when upgrading legacy contracts, migrating to modern syntax, or converting old patterns to current best practices. NOT for writing new contracts (use write-contracts) or fixing bugs.