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/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/commands/matt-dionis/claude-code-configs/validate-config)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/validate-config"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/validate-config/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/validate-config"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/validate-config.svg" alt="Reviewed on agentmods" width="80" 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.00008 | $0.00909 |
| Opus 5.5 | $0.00003 | $0.00364 |
| Sonnet 5.5 | $0.00002 | $0.00182 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
validate-config 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
!curl -s -X POST ${EVMAUTH_RPC_URL:-https://rpc.testnet.radiustech.xyz} \ How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Token-Gating Configuration
Comprehensive validation of your token-gated MCP server configuration.
Validation Checks
1. Environment Variables
# Check required variables
!echo "=== Environment Configuration ==="
!echo "Contract Address: ${EVMAUTH_CONTRACT_ADDRESS:-❌ NOT SET}"
!echo "Chain ID: ${EVMAUTH_CHAIN_ID:-❌ NOT SET}"
!echo "RPC URL: ${EVMAUTH_RPC_URL:-❌ NOT SET}"
!echo "Token ID: ${EVMAUTH_TOKEN_ID:-❌ NOT SET}"
!echo "Debug Mode: ${DEBUG:-✅ false (good for production)}"
!echo "Node Environment: ${NODE_ENV:-⚠️ NOT SET}"
2. Contract Address Validation
- Check format: 0x followed by 40 hexadecimal characters
- Verify it's a valid Ethereum address
- For testnet: Should be
0x5448Dc20ad9e0cDb5Dd0db25e814545d1aa08D96
3. Chain ID Validation
- Should be numeric
- For Radius Testnet: 1223953
- Must match the network your contract is deployed on
4. RPC Connection Test
# Test RPC endpoint
!curl -s -X POST ${EVMAUTH_RPC_URL:-https://rpc.testnet.radiustech.xyz} \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}' | \
jq -r 'if .result then "✅ RPC Connected - Chain: \(.result)" else "❌ RPC Connection Failed" end'
5. Dependencies Check
# Verify required packages
!echo "=== Required Dependencies ==="
!npm list fastmcp 2>/dev/null | grep fastmcp || echo "❌ fastmcp not installed"
!npm list @radiustechsystems/mcp-sdk 2>/dev/null | grep radius || echo "❌ Radius SDK not installed"
!npm list zod 2>/dev/null | grep zod || echo "❌ zod not installed"
!npm list viem 2>/dev/null | grep viem || echo "❌ viem not installed"
6. TypeScript Configuration
# Check TypeScript setup
![ -f "tsconfig.json" ] && echo "✅ tsconfig.json exists" || echo "❌ tsconfig.json missing"
!npx tsc --version 2>/dev/null || echo "❌ TypeScript not installed"
7. Server File Analysis
- Check for RadiusMcpSdk initialization
- Verify radius.protect() usage
- Ensure __evmauth parameter in schemas
- Validate error handling
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.
- 1mo ago First seen · 114 lines · 8 tokens per session scan A 4f5106affb00
validate-config is a command published in the GitHub repository Matt-Dionis/claude-code-configs (619 stars, last pushed 1y ago), licensed MIT. It adds 8 tokens to every session and 909 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
debug-user-tx
Replay a user's failing transaction on forked state and map the error to source.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
fix
Universal debugging and fix application with semantic code analysis.
audit-strict
Multi-pass consensus audit — runs the audit twice with different prompts, only reports consensus findings. Aggressively cuts false positives.