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 solanabr/solana-ai-kit --skill skillsgit clone --depth 1 https://github.com/solanabr/solana-ai-kitWrote 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/solanabr/solana-ai-kit/skills)<a href="https://agentmods.dev/skills/solanabr/solana-ai-kit/skills"><img src="https://agentmods.dev/badge/skills/solanabr/solana-ai-kit/skills/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/solanabr/solana-ai-kit/skills"><img src="https://agentmods.dev/badge/skills/solanabr/solana-ai-kit/skills.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.00068 | $0.05483 |
| Opus 5 | $0.00034 | $0.02742 |
| Sonnet 5 | $0.00014 | $0.01097 |
| Haiku 4.5 | $0.00007 | $0.00548 |
Grade C, and why
solana-dev scanned grade C with 2 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 11d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- ⚠ Its proxy/scan-deps/scan-secrets files contain `curl … | bash` binary installers (reaper/wraith/poltergeist, unpinned from `main`) — NEVER execute installers without explicit user consent Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- ⚠ Its proxy/scan-deps/scan-secrets files contain `curl … | bash` binary installers (reaper/wraith/poltergeist, unpinned from `main`) — NEVER execute installers without explicit user consent How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solana Development Skill Hub
Routes to the right skill file based on the task. Read the relevant section, follow the link, load that skill.
Source precedence (when multiple skills cover one topic):
.claude/rules/*are law for code style — always win (checked math, PDA bumps, nounwrap()/init_if_needed, reload-after-CPI, naming). No skill overrides a rule on style.- Protocol-OFFICIAL skill is primary for that protocol's API/SDK usage (jup-ag→Jupiter, metaplex-foundation→Metaplex, helius-labs→Helius).
- Foundation/platform skills (solana-dev) are primary for general concepts (Anchor, Pinocchio, testing, clients).
- sendai/community versions are secondary references — routed only when the official/foundation source lacks coverage.
One primary per row: each Task-Routing row points to exactly ONE primary target; secondaries live in section bodies, not the routing table.
Core Solana Development
Primary entry point — read first for any Solana program, frontend, testing, or client task:
- ext/solana-dev/skill/SKILL.md — Solana Foundation skill (framework-kit-first, Kit types, wallet-standard)
Key references within:
- programs/anchor.md — Anchor patterns, IDL, constraints (canonical)
- programs/pinocchio.md — Zero-copy, CU optimization (canonical)
- frontend-framework-kit.md — React hooks, wallet connection, @solana/kit UI
- kit-web3-interop.md — Kit ↔ web3.js boundary patterns
- testing.md — LiteSVM, Mollusk, Surfpool, CI
- security.md — Vulnerability categories, checklists
- idl-codegen.md — Codama/Shank client generation
- payments.md — Commerce Kit, Kora, Solana Pay
- resources.md — Official documentation links
What ships with it
7 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.
- 11d ago First seen · 249 lines · 68 tokens per session scan C d4ab7d2a08ab
solana-dev is a skill published in the GitHub repository solanabr/solana-ai-kit (101 stars, last pushed 21d ago), licensed MIT. It adds 68 tokens to every session and 5,483 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
jahro-logging
Reviews and improves Debug.Log usage in Unity C# projects following structured logging principles: context tags, severity contracts, boundary-based placement, and criticality tiers. Detects common antipatterns (naked Debug.Log, logging in Update, stringly-typed errors), adds missing logs at system/state/error/external…
jahro-migration
Analyzes existing debug systems (IMGUI menus, custom loggers, cheat frameworks, performance HUDs) and generates incremental migration plans to Jahro equivalents. Use when the user wants to replace a custom debug UI, migrate from an existing console or cheat system, switch to Jahro, or has OnGUI debug code they want to…
jahro-troubleshooting
Diagnoses common Jahro issues using decision trees: commands not appearing, watcher not updating, console not opening, snapshots failing, launch button missing. Use when the user reports something not working, missing, broken, or unexpected with Jahro, or when generated Jahro code doesn't behave as expected.
jahro-commands
Analyzes C# classes and generates [JahroCommand] attributes with correct syntax, RegisterObject patterns, and group organization. Use when the user wants to add runtime commands, cheats, or debug actions to Unity classes, or mentions JahroCommand, console commands, runtime cheats, or debug actions.
jahro-watcher
Analyzes C# fields and properties and generates [JahroWatch] attributes with groups and performance-safe patterns. Use when the user wants to monitor variables at runtime, add watchers, track game state, replace Debug.Log polling, or mentions JahroWatch, real-time inspection, or variable monitoring.
jahro-production
Configures Jahro lifecycle controls for safe production deployment including JAHRODISABLE, auto-disable, and build validation. Use when the user mentions production builds, release builds, disabling Jahro, shipping, CI/CD, lifecycle controls, or production safety.