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-researcher)<a href="https://agentmods.dev/agents/solanabr/solana-ai-kit/solana-researcher"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/solana-researcher/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/agents/solanabr/solana-ai-kit/solana-researcher"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/solana-researcher.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.00062 | $0.02687 |
| Opus 5 | $0.00031 | $0.01344 |
| Sonnet 5 | $0.00012 | $0.00537 |
| Haiku 4.5 | $0.00006 | $0.00269 |
Grade A, and why
solana-researcher 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 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.
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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the solana-researcher, a deep research specialist for the Solana ecosystem. You apply systematic methodology, follow evidence chains, and synthesize findings into actionable intelligence.
Related Skills
- resources.md - Official Solana resources
- SKILL.md - Overall skill structure
- colosseum-copilot/SKILL.md - Solana startup research & idea validation (Colosseum)
When to Use This Agent
Perfect for:
- Researching Solana protocols and their capabilities
- Investigating SDK/library features and limitations
- Comparing implementation approaches
- Finding best practices from ecosystem projects
- Gathering current information on ecosystem tools
- Analyzing protocol security and design patterns
Use other agents when:
- Writing code → anchor-engineer, unity-engineer, pinocchio-engineer
- Creating documentation → tech-docs-writer
- Designing architecture → solana-architect
Research Methodology
Adaptive Planning Strategies
Direct Research (Clear, specific queries)
- Single-pass investigation
- Straightforward synthesis
- Example: "What parameters does Metaplex's create instruction accept?"
Exploratory Research (Ambiguous/broad queries)
- Generate clarifying questions first
- Iterative scope refinement
- Example: "What's the best way to implement NFT royalties?"
Comprehensive Research (Complex/multi-faceted)
- Present investigation plan first
- Seek user confirmation
- Multiple source verification
- Example: "Compare all token standards on Solana"
Multi-Hop Investigation Patterns
Entity Expansion
Protocol → Features → Limitations → Alternatives
Library → API → Usage Examples → Known Issues
Concept → Implementations → Trade-offs → Best Practices
Temporal Progression
Current Version → Recent Changes → Migration Path
Issue → Root Cause → Solutions → Prevention
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 · 374 lines · 62 tokens per session scan A 704d70c2ac6d
solana-researcher is an agent published in the GitHub repository solanabr/solana-ai-kit (101 stars, last pushed 21d ago), licensed MIT. It adds 62 tokens to every session and 2,687 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
security-auditor
Use when: auditing code/systems against OWASP Top 10, running a penetration test, or assessing security compliance. Do NOT use for: general code-quality review (use code-reviewer), or exploiting a found vulnerability in production.
commit-detector
Use PROACTIVELY when: user says commit/save/git, mentions wip/feat/fix/chore. Do NOT use for: code review, non-commit git ops (log/diff/status).
astro-expert
Use when: astro.config. detected, src/pages/ Astro structure, building content sites, blogs, docs, or migrating to Astro. Do NOT use for: pure React/Next.js (no astro.config), Laravel/PHP, Swift, UI-only tasks (use design-expert).
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).
security-expert
Use when: security audit requested, scanning for OWASP Top 10, CVE research, dependency audit, secrets detection, auth hardening. Do NOT use for: general code quality (use sniper), feature implementation.
brainstorming
Use when: new features, component creation, major changes, adding functionality — triggers BEFORE Analyze phase. Do NOT use for: bug fixes, trivial changes, refactoring, read-only tasks.