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 skills add ValidatorsDAO/slv --skill slv-rpc-gatewaygit 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-gateway)<a href="https://agentmods.dev/skills/validatorsdao/slv/slv-rpc-gateway"><img src="https://agentmods.dev/badge/skills/validatorsdao/slv/slv-rpc-gateway/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/validatorsdao/slv/slv-rpc-gateway"><img src="https://agentmods.dev/badge/skills/validatorsdao/slv/slv-rpc-gateway.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 138 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Data Exfiltration · line 205 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00067 | $0.02690 |
| Opus 5.5 | $0.00027 | $0.01076 |
| Sonnet 5.5 | $0.00013 | $0.00538 |
| Haiku 4.5 | $0.00007 | $0.00269 |
Grade B, and why
slv-rpc-gateway scanned grade B with 2 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 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
5. Smoke test: `curl -X POST http://localhost:8889 -d '{"jsonrpc":"2.0",…}'`. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
5. Smoke test: `curl -X POST http://localhost:8889 -d '{"jsonrpc":"2.0",…}'`. How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLV RPC Gateway Skill
A unified JSON-RPC + WebSocket entry point that combines the per-call latency of of1 (yellowstone-faithful) with the bulk-analytics speed of jetstreamer's ClickHouse tables. Standard methods go to the underlying RPC; new methods are answered from a custom indexer.
client ── POST / ─► rpc-gateway ──► standard RPC (getTransaction, …) ── of1
└──► jet* (analytics) ── ClickHouse
└──► getTransactionsForAddress ── ClickHouse + of1
└──► getTransfersByAddress ── ClickHouse
client ── /ws ──► rpc-gateway ──► transactionSubscribe ── Yellowstone gRPC
└──► slotSubscribe (multi-source) ── multiplexed pubsub
└──► standard pubsub ── upstream pubsub WS
Why
| Layer | Component | Responsibility |
|---|---|---|
| Per-call (read 1 tx) | yellowstone-faithful (of1) |
getTransaction, getBlock, getBlockTime, getSignaturesForAddress |
| Cross-epoch analytics | jetstreamer + ClickHouse | aggregations over millions of txs |
| Per-address index | slv_gtfa_plugin + slv_transfers_plugin |
per-address tx / transfer lookups |
| Unified surface | rpc-gateway (this skill) | dispatch by method name, return JSON-RPC |
Without the gateway, clients have to know two endpoints and two protocols (JSON-RPC vs ClickHouse SQL). With it, everything is one JSON-RPC endpoint.
HTTP JSON-RPC methods
| Method | Backend | Notes |
|---|---|---|
| Standard Solana RPC | of1 | Forwarded transparently |
jetTopPrograms |
CH | Top-N programs by invocation count over a time window |
jetProgramStats |
CH | Time series for a single program (calls, errors, CU) |
jetSlotStats |
CH | Per-slot tx counts (single slot or range up to 100k) |
jetTpsTimeseries |
CH | Total + non-vote TPS in time buckets |
jetEpochSummary |
CH | Aggregate stats for one epoch |
getTransactionsForAddress |
CH (gtfa_tx_mentions) + of1 fan-out for full mode |
Per-address transaction index, signatures or full mode |
getTransfersByAddress |
CH (token_transfers + by_to MV) | Per-address SPL token transfer index, direction-aware |
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 · 214 lines · 67 tokens per session scan B 6d9412136708
slv-rpc-gateway is a skill published in the GitHub repository ValidatorsDAO/slv (96 stars, last pushed 7d ago), licensed Apache-2.0. It adds 67 tokens to every session and 2,690 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
solana-dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "fuzz my Solana program", "deploy to devnet", "send a v1 transaction", "support larger transactions", "fix maxSupportedTransactionVersion", or "explain…
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…
integrating-jupiter
Comprehensive guidance for integrating Jupiter APIs (Swap, Lend, Perps, Trigger, Recurring, Tokens, Price, Portfolio, Prediction Markets, Send, Studio, Lock, Routing). Use for endpoint selection, integration flows, error handling, and production hardening.
privy-integration
Integrates Privy authentication, embedded wallets, and agent payment protocols into web and agentic apps. Covers React SDK (PrivyProvider, hooks, wagmi), Node.js SDK, smart wallets (ERC-4337), x402 and MPP machine payments, Tempo chain, and agentic wallets with policies. Use when setting up Privy auth, creating…
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…