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 widnyana/eyay-toolkits --skill solana-accept-riskgit clone --depth 1 https://github.com/widnyana/eyay-toolkitsWrote 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/widnyana/eyay-toolkits/solana-accept-risk)<a href="https://agentmods.dev/skills/widnyana/eyay-toolkits/solana-accept-risk"><img src="https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/solana-accept-risk/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/widnyana/eyay-toolkits/solana-accept-risk"><img src="https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/solana-accept-risk.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.00443 |
| Opus 5 | $0.00028 | $0.00221 |
| Sonnet 5 | $0.00011 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
solana-accept-risk 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 12d 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.
What it actually says
Manage mainnet risk acceptance. Required before any mainnet write operations.
Review: $ARGUMENTS
Instructions
status (default)
- Check
SOLANA_ACCEPT_RISKenvironment variable. - If
true— show acceptance is active. - If not set — show that mainnet operations are blocked and how to accept.
accept
- Show risk disclosure:
- Transactions are permanent and irreversible
- Sending to wrong address = permanent loss
- No customer service or recovery
- User accepts full responsibility
- Ask user to confirm by typing
ACCEPT. - On confirmation — set
SOLANA_ACCEPT_RISK=trueand record timestamp. - Show safety reminders:
- Always simulate before executing
- Triple-check recipient addresses
- Start with tiny test amounts
- Keep keypair secure
revoke
- Confirm user wants to revoke.
- Unset
SOLANA_ACCEPT_RISK. - Confirm mainnet operations are now blocked.
- Tell user to run
/solana-accept-risk acceptto re-enable.
Mainnet safety gate
Before ANY mainnet write operation, check:
SOLANA_ACCEPT_RISKistrue- If not — refuse the operation and tell user to run
/solana-accept-risk
For large amounts on mainnet, request extra explicit confirmation showing:
- Recipient address
- Amount and approximate USD value
- That this is mainnet with real SOL
Scope
- Acceptance is per-session by default (resets on Claude Code restart).
- Can be persisted via plugin settings if user configures it.
- Does NOT affect devnet/testnet/localnet operations.
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.
- 12d ago First seen · 61 lines · 56 tokens per session scan A d67622c31051
solana-accept-risk is a skill published in the GitHub repository widnyana/eyay-toolkits (7 stars, last pushed 9d ago), licensed MIT. It adds 56 tokens to every session and 443 once invoked, about $0.0003 per session on Opus 5. 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-31.
Other skills, from other repositories
web3-protocol-gtm
Go-to-market strategy for web3 builders - protocols, products, services, and solo founders. Use when planning growth for a crypto protocol, building developer community, crafting CT narrative, planning ecosystem partnerships, preparing grant applications, launching tokens, pricing crypto-native products, or growing as…
solana-development
Build, test, deploy, and audit Solana programs with Anchor or native Rust, plus ZK Compression (Light Protocol). Use for Solana contracts, token operations, compute optimization, deployment, program audits, or compressed tokens and PDAs.
x402
Build internet-native payments with x402 - HTTP 402 for on-chain micropayments, no accounts or API keys. Use for paid APIs, paywalled content, agent payment flows, or per-call MCP tools. TypeScript, Python, and Go SDKs across EVM and Solana.
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…
metengine-data-agent
Real-time smart money analytics API for Polymarket prediction markets, Hyperliquid perpetual futures, and Meteora Solana LP/AMM pools. 63 endpoints. Pay-per-request via x402 on Solana Mainnet USDC. No API keys.
erc-8004
Build with ERC-8004 Trustless Agents - on-chain agent identity, reputation, validation, and discovery on EVM chains. Use when registering agents on-chain, building agent reputation, or using the Agent0 SDK. Triggers on ERC-8004 and Agent0.