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-server-procurementgit 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-server-procurement)<a href="https://agentmods.dev/skills/validatorsdao/slv/slv-server-procurement"><img src="https://agentmods.dev/badge/skills/validatorsdao/slv/slv-server-procurement/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-server-procurement"><img src="https://agentmods.dev/badge/skills/validatorsdao/slv/slv-server-procurement.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.00786 |
| Opus 5.5 | $0.00000 | $0.00314 |
| Sonnet 5.5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
slv-server-procurement 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 24d 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.
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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: slv-server-procurement
Server procurement and provisioning management for SLV users.
Overview
Figaro finds the perfect server for the user's needs and presents it attractively. Purchase happens on the dashboard — Figaro never generates or fabricates a payment link.
Primary MCP Tools (use these first)
1. Search Available VPS
call_mcp(tool_name="get_vps_search_available_vps", arguments={region: "amsterdam"})
Find available VPS instances by region.
2. Check BareMetal Availability
call_mcp(tool_name="get_baremetal_availability")
Check unassigned BareMetal subscriptions the user already has.
3. Send to checkout
There is no call_mcp tool for generating a payment link. Once the user confirms a choice, send them to https://dashboard.erpc.global to complete checkout.
Secondary MCP Tools
Server Product Lists
call_mcp(tool_name="get_baremetal_list_public_node_type", arguments={nodeType: "<TYPE>"})— List products by type
Server Types
get_baremetal_list_public_node_type accepts 6 nodeType values; server products live under APP, MV, and RPC (never pass a premium/top-tier suffix like MV+):
| nodeType | Use Case |
|---|---|
APP |
Testnet validators, dev/test, apps |
MV |
Mainnet validators — premium and top-tier hardware are separate products inside the MV list, not separate nodeType values |
RPC |
RPC nodes (Index RPC, gRPC Geyser, combos) |
Status Tracking
call_mcp(tool_name="get_baremetal_status")— Check user's assigned serverscall_mcp(tool_name="get_vps_status")— Check user's VPS statuscall_mcp(tool_name="get_vps_list_public")— List VPS plans
Mapping: User request -> nodeType
- "testnet validator" -> APP (128GB+ RAM minimum)
- "mainnet validator" -> MV (pick the higher-tier product from the MV list for premium/top-tier)
- "RPC node" / "gRPC node" -> RPC
- "dev server" / "app server" -> APP
Minimum specs for Solana nodes
- Testnet validator: 128GB RAM minimum
- Mainnet validator: 384GB RAM minimum
- gRPC Geyser only: 384GB RAM minimum
- Index RPC (without gRPC): 768GB RAM minimum
- Index RPC + gRPC: 1TB RAM minimum
What ships with it
2 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.
- 24d ago Changed · -4 lines 304aedbe8e55
- 1mo ago First seen · 78 lines · 0 tokens per session scan A a4d0b7c0aafc
slv-server-procurement is a skill published in the GitHub repository ValidatorsDAO/slv (96 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 786 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).