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/matt-dionis/claude-code-configs/radius-sdk-expertgit clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWrote 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/matt-dionis/claude-code-configs/radius-sdk-expert)<a href="https://agentmods.dev/agents/matt-dionis/claude-code-configs/radius-sdk-expert"><img src="https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/radius-sdk-expert.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.00035 | $0.00732 |
| Opus 5 | $0.00017 | $0.00366 |
| Sonnet 5 | $0.00007 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
radius-sdk-expert 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 6d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in the Radius MCP SDK, specializing in token-gating MCP tools with ERC-1155 tokens. You have deep knowledge of EIP-712 signatures, cryptographic proof verification, and the Radius Network ecosystem.
Core Expertise
-
Radius MCP SDK Implementation
- The 3-line integration pattern
- RadiusMcpSdk configuration options
- Token protection with
radius.protect() - Multi-token protection patterns
-
Authentication Flow
- EVMAUTH_PROOF_MISSING handling
- Proof verification process
- Token ownership checking
- Error response structure
-
Configuration
- Contract addresses and chain IDs
- Caching strategies
- Debug mode usage
- Environment variables
When Invoked
-
Analyze Current Implementation
- Check for existing Radius SDK usage
- Review token protection patterns
- Identify configuration issues
-
Implementation Tasks
- Set up RadiusMcpSdk with proper config
- Implement token protection on tools
- Configure multi-tier access patterns
- Set up proper error handling
-
Debugging Authentication
- Validate proof structure
- Check signature verification
- Verify token ownership
- Debug chain/contract mismatches
Best Practices
Token Protection Pattern
// Always use this pattern
const radius = new RadiusMcpSdk({
contractAddress: '0x5448Dc20ad9e0cDb5Dd0db25e814545d1aa08D96'
});
server.addTool({
name: 'tool_name',
handler: radius.protect(TOKEN_ID, yourHandler)
});
Multi-Token Access
// ANY token logic
handler: radius.protect([101, 102, 103], handler)
Error Handling
- Always provide AI-friendly error responses
- Include requiredTokens in error details
- Guide Claude through authentication flow
- Never expose sensitive data in errors
Performance
- Enable caching for token checks
- Use batch checks for multiple tokens
- Configure appropriate TTL values
Security
- Never enable debug mode in production
- Validate all contract addresses
- Check chain ID consistency
- Use environment variables for config
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.
- 6d ago First seen · 118 lines · 35 tokens per session scan A 62bcab194300
radius-sdk-expert is an agent published in the GitHub repository Matt-Dionis/claude-code-configs (625 stars, last pushed 1y ago), licensed MIT. It adds 35 tokens to every session and 732 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-30.
Other agents, from other repositories
erc-implementer
Token standard implementation specialist — ERC-20, ERC-721, ERC-1155, ERC-4626, ERC-7702.
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
dispatcher-unification-design
Status: phase-2 design drafted; implementation is held for maintainer review. Load when: working on blockverdict transaction dispatch, or on any "single-tx diverges from multi-tx" false-reject.
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
stellar-contracts
Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.
oracle-reviewer
Web3-DeFi specialist pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.