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/validatorsdao/slv/slv-rpcnpx skills add ValidatorsDAO/slv --skill slv-rpcgit clone --depth 1 https://github.com/ValidatorsDAO/slvWrote 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/validatorsdao/slv/slv-rpc)<a href="https://agentmods.dev/skills/validatorsdao/slv/slv-rpc"><img src="https://agentmods.dev/badge/skills/validatorsdao/slv/slv-rpc.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.00000 | $0.04818 |
| Opus 5 | $0.00000 | $0.02409 |
| Sonnet 5 | $0.00000 | $0.00964 |
| Haiku 4.5 | $0.00000 | $0.00482 |
Grade B, and why
slv-rpc scanned grade B 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo systemctl start of1-index-sync.service # ad-hoc sync How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLV RPC Skill
Ansible playbooks and Jinja2 templates for deploying and managing Solana RPC nodes (mainnet, testnet, devnet).
Supported RPC Types
| Type | Description |
|---|---|
RPC |
Standard RPC node |
Index RPC |
Full-index RPC node (with Old Faithful/yellowstone-faithful) |
Geyser gRPC |
RPC with Geyser gRPC streaming |
Index RPC + gRPC |
Full-index + gRPC streaming |
Directory Structure
ansible/
mainnet-rpc/ — Mainnet RPC playbooks
testnet-rpc/ — Testnet RPC playbooks
devnet-rpc/ — Devnet RPC playbooks
cmn/ — Shared common playbooks
jinja/
mainnet-rpc/ — Mainnet Jinja2 templates
testnet-rpc/ — Testnet Jinja2 templates
devnet-rpc/ — Devnet Jinja2 templates
cmn/ — Shared templates
Benchmarking Notes
Planned CLI shape
A natural future command shape is:
slv check geyserbench <options>
This would mirror the existing slv check grpc / slv check shreds style by passing arguments through to the installed benchmark binary.
geyserbench config generation
For shredstream and grpc benchmark flows, the agent should be able to generate config.toml from:
- benchmark type
- two endpoint URLs
- ERPC API key from
~/.slv/api.yml
If ~/.slv/api.yml does not contain the required ERPC API key, instruct the user to get a free key and configure it first.
Example config:
[config]
region = "frankfurt"
erpc_url = "https://edge.erpc.global"
erpc_api_key = "api-key"
transactions = 10000
account = "pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA"
commitment = "processed"
[[endpoint]]
name = "http://shreds-fra6-1.erpc.global"
url = "http://shreds-fra6-1.erpc.global"
kind = "shredstream"
[[endpoint]]
name = "http://shreds-turbo-fra-1.erpc.global"
url = "http://shreds-turbo-fra-1.erpc.global"
kind = "shredstream"
For gRPC benchmarks, use the same structure but set the endpoint kind to the appropriate gRPC-compatible type.
CLI Command ↔ Playbook Mapping
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 406 lines · 0 tokens per session scan B bcb793f7300f
slv-rpc is a skill published in the GitHub repository ValidatorsDAO/slv (89 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,818 tokens. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
stellar-forge
Eval-driven coding harness for building production Stellar dApps. Routes tasks to 6 specialist agents, verifies output with structured evals, steers on failure, e2e-tests with Stellar Agentic Kit hooks, and knowledge-graphs every project. Use when building any Stellar app — tokens, DeFi, NFTs, payment APIs, or full…
stellar-mcp
MCP (Model Context Protocol) tools for Stellar development. Gives Claude direct access to the Stellar blockchain, filesystem, GitHub, and Playwright through configured MCP servers. Use when querying chain data, deploying contracts, managing repos, or running e2e tests from within the agent.
alchemy-agentic-gateway
Use when accessing Alchemy APIs for RPC calls, token balances, NFT metadata, asset transfers, transaction simulation, or Alchemy-specific features. Also use when the user mentions "SIWE", "SIWS", "x402", "MPP", "mppx", or "agentic gateway" — this skill covers wallet-based auth flows for Alchemy's x402 and MPP…
alchemy-api
Integrates Alchemy blockchain APIs using an API key. Requires $ALCHEMYAPIKEY to be set; if unavailable, use the alchemy-agentic-gateway skill instead. Use when user asks about EVM JSON-RPC calls, token balances, NFT ownership or metadata, transfer history, token prices, portfolio data, transaction simulation…
rpcedge
Use rpc edge Solana trading infrastructure via MCP tools - doctor, RPC health, priority fees, epoch/leaders, latency compare, Yellowstone first-seen sample, endpoint map, and signed-transaction relay. Prefer when the user needs low-latency Solana RPC/gRPC/sender setup, fee pricing, or agent-ready infra with keys in…
Solana Agent Builder
Build AI-powered agents for Solana blockchain — trading bots, DeFi strategies, token analysis, and on-chain automation with TypeScript.