solana-vault-standard: Agent for Claude Code

.claude/agents/solana-qa-engineer.md

solana-qa-engineer is an agent for Claude Code from solanabr/solana-vault-standard. It costs 75 tokens per session (1,716 once invoked), scanned A, a copy of solana-qa-engineer, MIT.

A testing and quality-assurance specialist for Solana programs, which are applications running on the Solana blockchain. It covers isolated tests, multi-step tests, realistic local blockchain state, fuzz testing, resource measurement, and code quality.

In plain words
What is it for?
Use it to write or debug Rust and TypeScript tests, select Mollusk, LiteSVM, Surfpool, or Trident, test security boundaries, measure compute units, and review code quality.
Why use it?
It helps developers choose an appropriate testing approach and investigate failures, edge cases, security problems, and excessive compute use.

Agent for Claude Code

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

This is solanabr/solana-vault-standard's own configuration. It tells Claude Code how to work on solana-vault-standard itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything solana-vault-standard configures →

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

Reuse

Borrowing it

Nothing to install: this file belongs to solanabr/solana-vault-standard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/solanabr/solana-vault-standard/main/.claude/agents/solana-qa-engineer.md
Clone the repo
git clone --depth 1 https://github.com/solanabr/solana-vault-standard

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-vault-standard/solana-qa-engineer/github.svg)](https://agentmods.dev/agents/solanabr/solana-vault-standard/solana-qa-engineer)
Your own site
<a href="https://agentmods.dev/agents/solanabr/solana-vault-standard/solana-qa-engineer"><img src="https://agentmods.dev/badge/agents/solanabr/solana-vault-standard/solana-qa-engineer/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.

agentmods 80×15 button for solana-qa-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/solanabr/solana-vault-standard/solana-qa-engineer"><img src="https://agentmods.dev/badge/agents/solanabr/solana-vault-standard/solana-qa-engineer.svg" alt="Reviewed on agentmods" width="80" 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 100% copy Near-identical to another mod 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 10d ago against content hash 6c0ce1086669, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 10d 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

This is a copy

100% identical to solana-qa-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.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. 10d 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-vault-standard (24 stars, last pushed 5mo 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. It is 100% identical to solana-qa-engineer, differing in 0 lines, and is treated as a copy.