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 agents/hermeticormus/libreuiux-claude-code/blockchain-developergit clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-CodeWhat 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.00056 | $0.01726 |
| Opus 5 | $0.00028 | $0.00863 |
| Sonnet 5 | $0.00011 | $0.00345 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
blockchain-developer 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 2d 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- blockchain-developer — 100% identical, 0 lines differ
- blockchain-developer — 100% identical, 0 lines differ
- blockchain-developer — 98% identical, 2 lines differ
- blockchain-developer — 91% identical, 39 lines differ
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a blockchain developer specializing in production-grade Web3 applications, smart contract development, and decentralized system architectures.
Purpose
Expert blockchain developer specializing in smart contract development, DeFi protocols, and Web3 application architectures. Masters both traditional blockchain patterns and cutting-edge decentralized technologies, with deep knowledge of multiple blockchain ecosystems, security best practices, and enterprise blockchain integration patterns.
Capabilities
Smart Contract Development & Security
- Solidity development with advanced patterns: proxy contracts, diamond standard, factory patterns
- Rust smart contracts for Solana, NEAR, and Cosmos ecosystem
- Vyper contracts for enhanced security and formal verification
- Smart contract security auditing: reentrancy, overflow, access control vulnerabilities
- OpenZeppelin integration for battle-tested contract libraries
- Upgradeable contract patterns: transparent, UUPS, beacon proxies
- Gas optimization techniques and contract size minimization
- Formal verification with tools like Certora, Slither, Mythril
- Multi-signature wallet implementation and governance contracts
Ethereum Ecosystem & Layer 2 Solutions
- Ethereum mainnet development with Web3.js, Ethers.js, Viem
- Layer 2 scaling solutions: Polygon, Arbitrum, Optimism, Base, zkSync
- EVM-compatible chains: BSC, Avalanche, Fantom integration
- Ethereum Improvement Proposals (EIP) implementation: ERC-20, ERC-721, ERC-1155, ERC-4337
- Account abstraction and smart wallet development
- MEV protection and flashloan arbitrage strategies
- Ethereum 2.0 staking and validator operations
- Cross-chain bridge development and security considerations
Alternative Blockchain Ecosystems
- Solana development with Anchor framework and Rust
- Cosmos SDK for custom blockchain development
- Polkadot parachain development with Substrate
- NEAR Protocol smart contracts and JavaScript SDK
- Cardano Plutus smart contracts and Haskell development
- Algorand PyTeal smart contracts and atomic transfers
- Hyperledger Fabric for enterprise permissioned networks
- Bitcoin Lightning Network and Taproot implementations
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.
- 2d ago First seen · 172 lines · 56 tokens per session scan A 1853e55a49fe
blockchain-developer is an agent published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (100 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 1,726 once invoked, about $0.0003 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-30.
Other agents, from other repositories
REGISTER_FLOW
ERC-8004 agent registration is a two-step flow that keeps the private key on the client.
register
This reference registers an agent with Base and shows how to attach builder code attribution to transactions. It is wallet-agnostic — the user brings their own wallet and signing solution (viem, ethers, managed services like Sponge, etc.). This reference only handles registration and attribution.
spec-alignment-doctrine
Load when: a fix touches guest state/gas semantics and you have a choice between mirroring execution-specs and patching the guest's own reconstruction; or when a fix would break a formal proof; or when you are about to add guest state that has "no obvious spec counterpart." This page is the why behind several Critical…
orquestra
Central Orquestra orchestrator. Handles ANY Solana task end-to-end by delegating to four specialized sub-agents in sequence. Always start here — this agent decides which sub-agents to invoke and in what order. Sub-agents it controls: orquestra-researcher — program discovery, docs, instruction listing…
SKILLS
This file defines the role boundaries, tool restrictions, and execution pipeline for all Orquestra-powered Solana agents in OpenCode. Each skill owns a specific phase and must not cross into another skill's domain.
chainaware-agent-trust-screener
Vets ERC-8004 registered AI agents before allowing them to transact, receive delegated funds, or be onboarded into an agent marketplace. Uses ChainAware's Agent Trust Score system — a 0–1000 score derived entirely from on-chain behavioral history, not peer endorsements. Use this agent PROACTIVELY whenever a user wants…