slv-irq-tuning

slv-irq-tuning is a skill for Claude Code, Codex from ValidatorsDAO/slv. It costs 79 tokens per session (980 once invoked), scanned B, original, Apache-2.0.

A Linux network and storage tuning procedure for Solana validator, RPC, and Shredstream nodes. It adjusts network interrupt handling, packet queues, NVMe queues, kernel buffers, memory swapping, and file-descriptor limits.

In plain words
What is it for?
Use it to prepare a node for high UDP, TCP, gRPC, or Shredstream traffic and to distribute network work across CPUs; changing NVMe queue settings requires a reboot.
Why use it?
It helps prevent packet drops, queue overflows, swapping, and too few open-file slots during heavy traffic.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare a node for high UDP, TCP, gRPC, or Shredstream traffic and to distribute network work across CPUs; changing NVMe queue settings requires a reboot.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/validatorsdao/slv/slv-irq-tuning
Install

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.

Any agent
npx skills add ValidatorsDAO/slv --skill slv-irq-tuning
Clone the repo
git clone --depth 1 https://github.com/ValidatorsDAO/slv

Made for: Claude Code, Codex.

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.

agentmods badge for slv-irq-tuning

README.md
[![agentmods](https://agentmods.dev/badge/skills/validatorsdao/slv/slv-irq-tuning/github.svg)](https://agentmods.dev/skills/validatorsdao/slv/slv-irq-tuning)
Your own site
<a href="https://agentmods.dev/skills/validatorsdao/slv/slv-irq-tuning"><img src="https://agentmods.dev/badge/skills/validatorsdao/slv/slv-irq-tuning/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.

agentmods 80×15 button for slv-irq-tuning

Your own site · 80×15
<a href="https://agentmods.dev/skills/validatorsdao/slv/slv-irq-tuning"><img src="https://agentmods.dev/badge/skills/validatorsdao/slv/slv-irq-tuning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 980 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 16 findings, up to high

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 →

  • high Tool Misuse · line 63
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Tool Misuse · line 64
    Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
    Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
  • high Tool Misuse · line 65
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Tool Misuse · line 66
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Tool Misuse · line 71
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • medium Privilege Escalation · line 62
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Privilege Escalation · line 63
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Privilege Escalation · line 64
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Privilege Escalation · line 70
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Privilege Escalation · line 71
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Rogue Agent · line 64
    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 Privilege Escalation · line 65
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Privilege Escalation · line 66
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Privilege Escalation · line 67
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Privilege Escalation · line 68
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Privilege Escalation · line 69
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00079 $0.00980
Opus 5 $0.00039 $0.00490
Sonnet 5 $0.00016 $0.00196
Haiku 4.5 $0.00008 $0.00098

Measured 9d ago against content hash 64014c526451, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

slv-irq-tuning 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 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo systemctl disable vs2-irq-tune.service
oss-skills/slv-irq-tuning/SKILL.md · 74 lines

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.

SLV IRQ & Network Tuning Skill

Removes NIC IRQ imbalance and applies Solana-friendly kernel parameters. Runs as part of slv v init / slv r init after the SSH connection check, alongside SMT disable and performance boost.

What it applies

# Item Effect Reboot
1 NIC IRQ 1:1 pinning Distributes NET_RX softirq evenly across all CPUs No
2 RPS/XPS enable Software-level packet distribution No
3 NIC ring buffer → 8192 (max) Prevents packet drops during bursts No
4 NVMe queues = ncores Stops queues from being assigned to offline CPUs Yes
5 sysctl: UDP/TCP buffers 128MB Prevents drops on Shredstream / gRPC No
6 sysctl: vm.swappiness → 1 Avoids swapping under memory pressure No
7 sysctl: netdev_max_backlog → 50000 Prevents NIC → kernel queue overflow No
8 THP (Transparent Huge Pages) → never Avoids latency spikes No
9 ulimit nofile → 1000000 Prevents fd exhaustion No (new sessions only)
  • ansible/cmn/irq_tune.yml — applies items 1-9 above
  • ansible/cmn/files/vs2-irq-tune.sh — re-applies NIC IRQ pin + RPS/XPS + ring + THP at boot (systemd oneshot)
  • ansible/cmn/files/vs2-irq-tune.service — systemd unit for the above
  • ansible/cmn/files/99-vs2-solana.conf — sysctl parameters
  • ansible/cmn/files/99-vs2-solana-limits.conf/etc/security/limits.d/
  • ansible/cmn/files/vs2-limits.conf — systemd DefaultLimitNOFILE drop-in

Run it

Normally invoked through cmn/optimize_node.yml together with SMT disable and CPU boost. Standalone:

ansible-playbook -i inventory.yml cmn/irq_tune.yml --limit <host>

Only sets need_reboot=true when NVMe queue parameters in GRUB had to change. The orchestrator reboots the host when needed.

Verification

Check Expected
NIC IRQ queue N → CPU N 1:1 mapping
RPS (bond0/vlan) ffff etc.
NIC ring buffer RX: 8192, TX: 8192
NVMe IRQ on offline CPU none
net.core.rmem_max / wmem_max 134217728
net.core.netdev_max_backlog 50000
vm.swappiness 1
THP [never]
GRUB has nvme.io_queues=N physical core count
vs2-irq-tune.service active (exited)
irqbalance inactive (disabled)

Read the full file on GitHub · 74 lines

Changes

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.

  1. 9d ago First seen · 74 lines · 79 tokens per session scan B 64014c526451

Subscribe to this mod's changes

slv-irq-tuning is a skill published in the GitHub repository ValidatorsDAO/slv (89 stars, last pushed 4d ago), licensed Apache-2.0. It adds 79 tokens to every session and 980 once invoked, about $0.0004 per session on Opus 5. 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.

Related

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…

rylsherdamz-rgb/stellar-forge · 82 tokens

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.

rylsherdamz-rgb/stellar-forge · 61 tokens

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…

moonpay/skills · 101 tokens

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…

moonpay/skills · 100 tokens

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…

rpc-edge/rpcedge-toolkit · 76 tokens

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).

Starchild-ai-agent/official-skills · 57 tokens