solana-qa-engineer

solana-qa-engineer is an agent for Claude Code from solanabr/solana-ai-kit. It costs 75 tokens per session (1,716 once invoked), scanned A, original, MIT.

A testing and quality-assurance specialist for Solana programs. It helps choose and use tests that check individual instructions, complete instruction flows, realistic blockchain state, and unusual or hostile inputs.

In plain words
What is it for?
Use it to write tests, select testing tools, debug failures, measure compute-unit use, fuzz for edge cases, and run security checks.
Why use it?
It gives Solana projects a structured way to find broken behavior, security problems, excessive compute use, and inconsistent code quality.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is svm.add_program(program_id, include_bytes!("../target/deploy/program.so"));.

Good fit Use it to write tests, select testing tools, debug failures, measure compute-unit use, fuzz for edge cases, and run security checks.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/solanabr/solana-ai-kit
agentmods
npx agentmods add agents/solanabr/solana-ai-kit/solana-qa-engineer

Made for: Claude Code.

Wrote 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.

agentmods badge for solana-qa-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/solana-qa-engineer.svg)](https://agentmods.dev/agents/solanabr/solana-ai-kit/solana-qa-engineer)
Your own site
<a href="https://agentmods.dev/agents/solanabr/solana-ai-kit/solana-qa-engineer"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/solana-qa-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 75 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,716 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.01716
Opus 5 $0.00037 $0.00858
Sonnet 5 $0.00015 $0.00343
Haiku 4.5 $0.00007 $0.00172

Measured 8d ago against content hash 6c0ce1086669, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

solana-qa-engineer 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 8d 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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

.claude/agents/solana-qa-engineer.md · 242 lines

How it starts

The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a solana-qa-engineer, a testing and quality assurance specialist for Solana programs. You own all testing frameworks, CU profiling, security testing, and code quality standards.

Core Competencies

Domain Expertise
Unit Testing Mollusk - fast, isolated instruction tests
Integration Testing LiteSVM - multi-instruction flows
Realistic State Surfpool - mainnet/devnet state locally
Fuzz Testing Trident - edge case and security discovery
CU Profiling Benchmarking, optimization verification
Code Quality AI slop removal, style consistency

Testing Framework Selection

Framework Speed Use Case When to Use
Mollusk ⚡ Fastest Unit tests Single instruction, CU measurement
LiteSVM ⚡ Fast Integration Multi-instruction, no validator
Surfpool 🚀 Fast Realistic state Testing with mainnet programs/state
Trident 🐢 Slow Fuzz testing Security, edge cases, property tests
anchor test 🐢 Slowest Full E2E Final integration before deploy

Testing Strategy by Project Phase

Development:  Mollusk (fast iteration)
Integration:  LiteSVM + Surfpool (flow testing)
Pre-deploy:   Trident (10+ min fuzz) + anchor test
Security:     Trident + manual audit

Mollusk Unit Test Pattern

#[cfg(test)]
mod tests {
    use mollusk_svm::Mollusk;
    use solana_sdk::{account::Account, pubkey::Pubkey, instruction::Instruction};

    #[test]
    fn test_instruction() {
        let program_id = Pubkey::new_unique();
        let mollusk = Mollusk::new(&program_id, "target/deploy/program.so");

        let instruction = Instruction {
            program_id,
            accounts: vec![],
            data: vec![0],
        };

        let result = mollusk.process_instruction(&instruction, &[]);
        
        assert!(result.program_result.is_ok());
        println!("CU consumed: {}", result.compute_units_consumed);
        assert!(result.compute_units_consumed < 10_000);
    }
}

Read the full file on GitHub · 242 lines

Changes

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.

  1. 8d ago First seen · 242 lines · 75 tokens per session scan A 6c0ce1086669

Subscribe to this mod's changes

solana-qa-engineer is an agent published in the GitHub repository solanabr/solana-ai-kit (101 stars, last pushed 18d ago), licensed MIT. It adds 75 tokens to every session and 1,716 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-30.

Related

Other agents, from other repositories

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).

fusengine/agents · 60 tokens

svg-verifier

Visually verify a rendered SVG animation in chrome-devtools MCP and return a tight verdict (≤100 words). Specialized for the /svg-verify skill's isolated-context phase. Use when the calling thread needs an objective read on motion / timing / quality without drowning in screenshot bytes.

ChanMeng666/svg-animation-studio · 64 tokens

verification-runner

Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.

oliver-kriska/claude-elixir-phoenix · 44 tokens

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

codebase-explorer

Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…

testdouble/han · 75 tokens

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).

fusengine/agents · 63 tokens