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-smt-disablenpx skills add ValidatorsDAO/slv --skill slv-smt-disablegit 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-smt-disable)<a href="https://agentmods.dev/skills/validatorsdao/slv/slv-smt-disable"><img src="https://agentmods.dev/badge/skills/validatorsdao/slv/slv-smt-disable.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.1 | $0.00044 | $0.00365 |
| Opus 5 | $0.00022 | $0.00182 |
| Sonnet 5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade B, and why
slv-smt-disable 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 5d 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 sed -i 's/ nosmt=force//' /etc/default/grub What it actually says
SLV SMT (Hyper-Threading) Disable Skill
Solana validator / RPC throughput is dominated by single-thread instruction performance, so disabling SMT consistently produces higher and more stable performance. Applied during slv v init / slv r init as part of the tuning phase.
How it works
Adds nosmt=force to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and runs update-grub. After reboot, the kernel only schedules on one logical thread per physical core.
Related ansible playbook
ansible/cmn/smt_disable.yml— appendsnosmt=forceto GRUB and runsupdate-grub- Idempotency marker:
/var/lib/slv/.smt_disabled
Standalone run
ansible-playbook -i inventory.yml cmn/smt_disable.yml --limit <host>
Sets need_reboot=true only when GRUB actually changed; the orchestrator reboots when needed.
Verification
# on the host
cat /proc/cmdline # should contain nosmt=force
lscpu | grep -E 'Thread|Core|Socket' # Thread(s) per core: 1
Rollback
sudo sed -i 's/ nosmt=force//' /etc/default/grub
sudo update-grub
sudo rm /var/lib/slv/.smt_disabled
sudo reboot
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.
- 5d ago First seen · 43 lines · 44 tokens per session scan B 5e1afe7aa498
slv-smt-disable is a skill published in the GitHub repository ValidatorsDAO/slv (89 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session and 365 once invoked, about $0.0002 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.
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-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).