Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/unique-divine/jiyuu/evm-rpc)<a href="https://agentmods.dev/skills/unique-divine/jiyuu/evm-rpc"><img src="https://agentmods.dev/badge/skills/unique-divine/jiyuu/evm-rpc/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/skills/unique-divine/jiyuu/evm-rpc"><img src="https://agentmods.dev/badge/skills/unique-divine/jiyuu/evm-rpc.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.00066 | $0.03375 |
| Opus 5 | $0.00033 | $0.01688 |
| Sonnet 5 | $0.00013 | $0.00675 |
| Haiku 4.5 | $0.00007 | $0.00337 |
Grade A, and why
evm-rpc 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 9d 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 \ How it starts
The opening of the file, as written. The whole thing — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EVM RPC: Receipt and Trace Playbook
Use this skill for EVM transaction debugging with JSON-RPC.
Quick Start
Set a hash and endpoint, then run receipt first and trace second.
evm_tx="0xYOUR_evm_tx"
EVM_RPC="https://evm-rpc.archive.testnet-2.nibiru.fi"
curl -s -X POST \
-H "Content-Type: application/json" \
--data "{\"jsonrpc\":\"2.0\",\"method\":\"eth_getTransactionReceipt\",\"params\":[\"$evm_tx\"],\"id\":1}" \
"$EVM_RPC" | jq
curl -s -X POST \
-H "Content-Type: application/json" \
--data "{\"jsonrpc\":\"2.0\",\"method\":\"debug_traceTransaction\",\"params\":[\"$evm_tx\",{\"tracer\":\"callTracer\"}],\"id\":1}" \
"$EVM_RPC" | jq
Endpoint Map - Nibiru Examples
Chain-agnostic rule: methods determine endpoint family.
| Purpose | Example endpoint | Methods |
|---|---|---|
| EVM JSON-RPC (mainnet) | https://evm-rpc.nibiru.fi |
eth_*, debug_*, net_*, web3_* |
| EVM JSON-RPC archive (mainnet) | https://evm-rpc.archive.nibiru.fi |
historical reads, tracing |
| EVM JSON-RPC archive (testnet) | https://evm-rpc.archive.testnet-2.nibiru.fi |
testnet tracing and historical reads |
| Comet RPC archive (mainnet) | https://rpc.archive.nibiru.fi |
/block_results, /consensus_params |
| Comet RPC archive (testnet) | https://rpc.archive.testnet-2.nibiru.fi |
/block_results, /consensus_params |
Rules:
- Run
eth_*anddebug_*only on EVM RPC endpoints. - Run
/block_resultsand/consensus_paramsonly on Comet RPC endpoints. - Prefer archive endpoints for old heights/hashes and tracing workflows.
Basic Queries (Health / Identity)
web3_clientVersion
Queries the traceability info like the client name, version, Git commit, Go version, runtime architecture, and build tags.
curl -X POST https://evm-rpc.nibiru.fi \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "web3_clientVersion",
"params": [],
"id": 1
}'
The response looks like this: "Nibiru 2.6.0: Compiled at Git commit 3cf97e3468f8ce922c8760f839f8f336ca0c37f4 using Go go1.24.5, arch amd64, and build tags (netgo osusergo ledger static rocksdb pebbledb muslc)"
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.
- 9d ago First seen · 345 lines · 66 tokens per session scan A 80089fec18d6
evm-rpc is a skill published in the GitHub repository Unique-Divine/jiyuu (6 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 3,375 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-08-31.
Other skills, from other repositories
code-changes
Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea. MUST be invoked at the start of such a task, before reading or writing any code. Defines how to analyze first, gate on user approval, plan, pick the…
pi-loop-forensics
Diagnose pi-go agent loops and degenerate turns — "agent loop aborted", runaway thinking with no tool calls, repeated phrases. Discriminates genuine model repetition collapse from a race, a tool-parse failure, or a too-low guard, and A/B replays a seed session across providers.
nightly-session-watch
Nightly sweep of the last 24h of pi-go sessions — anomalous runs, loop aborts, tool error rates, token waste, real prompt-token spend, and whether the observation and palace pipelines are still recording. Triages each finding to the specialist skill that diagnoses it. Use for an unattended daily health check, or on…
config-loader-helper
Diagnose configuration-related failures, enumerate required env vars, and guide safe local test setup (no secrets).
code-navigation
Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.
fix-suggester
Diagnose failures and propose minimal, test-backed fixes with verification and rollback instructions.