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-squads-upgradegit 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-squads-upgrade)<a href="https://agentmods.dev/skills/widnyana/eyay-toolkits/solana-squads-upgrade"><img src="https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/solana-squads-upgrade/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-squads-upgrade"><img src="https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/solana-squads-upgrade.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.00089 | $0.01307 |
| Opus 5 | $0.00044 | $0.00654 |
| Sonnet 5 | $0.00018 | $0.00261 |
| Haiku 4.5 | $0.00009 | $0.00131 |
Grade A, and why
Solana Squads Upgrade 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 13d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solana Squads Upgrade
Automate Solana program upgrades through Squads v4 multisig using the squads-program-action GitHub Action. Covers configuration, transaction building, and the full upgrade lifecycle from CI to on-chain execution.
When to Use
- Setting up CI/CD for Solana program deployments with multisig governance
- Creating GitHub Actions workflows that submit upgrade proposals to Squads
- Configuring Anchor IDL or program-metadata updates alongside program upgrades
- Debugging failed Squads upgrade proposals
- Understanding the instruction flow: buffer -> multisig proposal -> approval -> execution
Architecture Overview
Creates a Squads vault transaction (multisig proposal), not a direct on-chain upgrade.
CI Pipeline
-> squads-program-action creates vault transaction
-> Transaction appears in Squads UI (https://v4.squads.so/)
-> Team members review + approve
-> Squads executes: program upgrade + optional IDL + optional PDA verification
Key constraint: the provided keypair only needs transaction creation permission (voter role). The actual upgrade authority comes from the Squads vault PDA.
Action Inputs Reference
Required
| Input | Description |
|---|---|
rpc |
Solana RPC URL |
program |
Program ID to upgrade |
buffer |
Buffer account containing the new program bytecode |
multisig |
Squads v4 multisig address |
keypair |
Byte array of keypair with voter permission. Format: [23,42,53...] |
Optional
| Input | Default | Description |
|---|---|---|
idl-buffer |
— | Anchor IDL buffer address |
metadata-buffer |
— | program-metadata IDL buffer (alternative to idl-buffer) |
pda-tx |
— | Base64 encoded PDA verification transaction |
priority-fee |
100000 |
Priority fee in lamports |
vault-index |
0 |
Squads vault index |
Important: idl-buffer and metadata-buffer are mutually exclusive. Use idl-buffer for Anchor programs, metadata-buffer for non-Anchor programs or as a modern alternative.
What ships with it
3 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.
- 13d ago First seen · 115 lines · 89 tokens per session scan A c527921577ef
Solana Squads Upgrade is a skill published in the GitHub repository widnyana/eyay-toolkits (7 stars, last pushed 10d ago), licensed MIT. It adds 89 tokens to every session and 1,307 once invoked, about $0.0004 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
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
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.
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.
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…