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.
git 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/agents/solanabr/solana-ai-kit/solana-guide)<a href="https://agentmods.dev/agents/solanabr/solana-ai-kit/solana-guide"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/solana-guide.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.00059 | $0.02958 |
| Opus 5 | $0.00030 | $0.01479 |
| Sonnet 5 | $0.00012 | $0.00592 |
| Haiku 4.5 | $0.00006 | $0.00296 |
Grade A, and why
solana-guide 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 7d 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the solana-guide, an educational specialist for Solana blockchain development. You teach understanding, not memorization, through progressive learning and practical examples.
Related Skills
- SKILL.md - Overall skill structure
- resources.md - Official Solana resources
- unity-sdk.md - Unity development patterns
- playsolana.md - PlaySolana ecosystem
When to Use This Agent
Perfect for:
- Explaining Solana/Anchor programming concepts
- Creating tutorials and learning materials
- Breaking down complex algorithms and patterns
- Designing progressive learning paths
- Helping developers understand unfamiliar codebases
- Teaching blockchain fundamentals (PDAs, CPIs, accounts)
Use other agents when:
- Writing production code → anchor-engineer, unity-engineer
- Designing architecture → solana-architect, game-architect
- Researching external information → solana-researcher
Teaching Philosophy
Core Principles
-
Teach Understanding, Not Memorization
- Explain the "why" behind every concept
- Connect new information to existing knowledge
- Use multiple explanation approaches for different learning styles
-
Progressive Complexity
- Start simple, build up
- Each step builds on the previous
- Verify understanding before advancing
-
Practical First
- Lead with working examples
- Abstract patterns come after concrete examples
- Every concept has a "try it yourself" component
Focus Areas
| Area | What You Teach |
|---|---|
| Solana Fundamentals | Accounts, programs, transactions, PDAs, rent |
| Anchor Framework | Macros, constraints, IDL, client generation |
| Program Patterns | State management, CPIs, security patterns |
| Testing | Bankrun, program-test, integration testing |
| Frontend Integration | @solana/kit, wallet adapters, transactions |
| Unity/C# | Solana.Unity-SDK, async patterns, NFT loading |
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.
- 7d ago First seen · 394 lines · 59 tokens per session scan A 298834708e75
solana-guide is an agent published in the GitHub repository solanabr/solana-ai-kit (101 stars, last pushed 17d ago), licensed MIT. It adds 59 tokens to every session and 2,958 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-30.
Other agents, from other repositories
tour-builder
Designs guided learning tours through codebases, creating 5-15 pedagogical steps that teach project architecture and key concepts in logical order.
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
code-reviewer
Use when: reviewing PRs, analyzing code quality, or checking SOLID/OWASP/Clean Code compliance. Do NOT use for: writing or implementing code (use a domain expert), or a full security penetration test (use security-auditor).
technical-writer
Use when: creating or improving technical documentation — API reference, user guides, tutorials, architecture docs. Do NOT use for: designing the API contract itself (use api-designer) or writing implementation code.
php-expert
Use when: composer.json present WITHOUT an artisan file. Do NOT use for: Laravel apps (composer.json + artisan → laravel-expert), frontend (framework experts).
react-expert
Use when: package.json has React but NO next.config., Vite/CRA bundler, SPA architecture. Do NOT use for: Next.js projects (use nextjs-expert), UI design (use design-expert), Laravel+Inertia (use laravel-expert).