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-validatorgit 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-validator)<a href="https://agentmods.dev/skills/validatorsdao/slv/slv-validator"><img src="https://agentmods.dev/badge/skills/validatorsdao/slv/slv-validator/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-validator"><img src="https://agentmods.dev/badge/skills/validatorsdao/slv/slv-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.06706 |
| Opus 5.5 | $0.00000 | $0.02682 |
| Sonnet 5.5 | $0.00000 | $0.01341 |
| Haiku 4.5 | $0.00000 | $0.00671 |
Grade A, and why
slv-validator 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 yesterday.
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 — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLV Validator Skill
Ansible playbooks and Jinja2 templates for deploying and managing Solana validators (mainnet and testnet).
Supported Validator Types
| Type | Description |
|---|---|
jito |
Jito MEV client (default for mainnet) |
allnodes-jito |
Allnodes-Jito (jito fork with snapshot/voting/POH/SHA-NI patches) |
agave |
Standard Agave validator |
firedancer-agave |
Firedancer with Agave consensus. Testnet only: refused on mainnet during the Alpenglow migration |
firedancer-jito |
Firedancer with Jito consensus. Testnet only: refused on mainnet during the Alpenglow migration |
Alpenglow starts on mainnet at epoch 1064, and Firedancer and Frankendancer are not
supported during the migration. A mainnet voting validator is agave, jito or
allnodes-jito: mainnet init.yml and init-firedancer.yml refuse the Firedancer types
before anything is changed, and slv v setup:firedancer and slv v update:firedancer
refuse on mainnet.
Directory Structure
ansible/
mainnet-validator/ — Mainnet validator playbooks
testnet-validator/ — Testnet validator playbooks
cmn/ — Shared common playbooks
jinja/
mainnet-validator/ — Mainnet Jinja2 templates
testnet-validator/ — Testnet Jinja2 templates
cmn/ — Shared templates
CLI Command ↔ Playbook Mapping
The slv v CLI commands map directly to these playbooks. {net} = mainnet-validator or testnet-validator.
| CLI Command | Playbook | Description |
|---|---|---|
slv v init |
(no playbook — interactive prompts) | Generate ~/.slv/inventory.<network>.validators.yml |
slv v deploy |
{net}/init.yml |
Full node initialization and deployment |
slv v start |
{net}/start_node.yml |
Start validator |
slv v stop |
{net}/stop_node.yml |
Stop validator |
slv v restart |
{net}/restart_node.yml |
Graceful restart (agave-validator exit, then systemd) |
slv v build:solana |
{net}/install_solana.yml |
Build Solana from source (dispatches by validator_type) |
slv v install:solana |
cmn/install_solana.yml |
Install Solana binary (deprecated, prefer build) |
slv v setup:firedancer |
{net}/setup_firedancer.yml |
Setup/update Firedancer. Testnet only: refused on mainnet (Alpenglow) |
slv v update:firedancer |
{net}/update_firedancer.yml |
Update Firedancer binary. Testnet only: refused on mainnet (Alpenglow) |
slv v update:script |
{net}/update_startup_config.yml |
Re-render start-validator.sh from template |
slv v set:identity -p <host> |
{net}/set_identity_key.yml |
Set validator identity key on one host |
slv v set:unstaked |
{net}/set_unstaked_key.yml |
Switch to unstaked identity |
slv v register:bls |
(no playbook — solana CLI) | Register the BLS pubkey on each vote account (SIMD-0387). Also auto-runs at the end of slv v deploy |
slv v get:snapshot |
{net}/wget_snapshot.yml |
Download snapshot via aria2c |
slv v cleanup |
cmn/rm_ledger.yml |
Remove ledger/snapshot files |
slv disable pwd-login |
cmn/disable_pwd_login.yml |
Disable SSH password authentication |
slv v switch |
{net}/nodowntime_migrate.yml |
Zero-downtime identity migration (auto-swaps inventory) |
slv v list |
(no playbook) | List validators (CLI only) |
slv v gen:vote-account |
(no playbook) | Create vote account (solana CLI) |
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.
- yesterday Changed · +13 lines adaef31969a1
- 4d ago Changed 57c1f2571256
- 1mo ago First seen · 413 lines · 0 tokens per session scan A 71b244f72df7
slv-validator is a skill published in the GitHub repository ValidatorsDAO/slv (96 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 6,706 tokens. 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 skills, from other repositories
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…
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.
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-dev
Solana development: Anchor and Pinocchio programs, Kit clients, wallet flows, testing. Use when building a Solana dapp or program (e.g. write Anchor escrow, create SPL token, wallet-standard login, debug PDA, deploy to devnet).