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.
git clone --depth 1 https://github.com/GeckoVision/gecko-surfnpx agentmods add agents/geckovision/gecko-surf/solana-qa-engineerWrote 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/geckovision/gecko-surf/solana-qa-engineer)<a href="https://agentmods.dev/agents/geckovision/gecko-surf/solana-qa-engineer"><img src="https://agentmods.dev/badge/agents/geckovision/gecko-surf/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.
<a href="https://agentmods.dev/agents/geckovision/gecko-surf/solana-qa-engineer"><img src="https://agentmods.dev/badge/agents/geckovision/gecko-surf/solana-qa-engineer.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.00075 | $0.01764 |
| Opus 5 | $0.00037 | $0.00882 |
| Sonnet 5 | $0.00015 | $0.00353 |
| Haiku 4.5 | $0.00007 | $0.00176 |
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.
This is a copy
89% identical to solana-qa-engineer — 3 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.
How it starts
The opening of the file, as written. The whole thing — 245 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.
Related Skills & Commands
- testing.md - Testing strategy and framework selection
- security.md - Security testing checklist
- /test-rust - Rust testing command
- /test-ts - TypeScript testing command
- /audit-solana - Security audit command
- ext/qedgen/SKILL.md - Formal verification with Lean 4
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
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.
- 8d ago First seen · 245 lines · 75 tokens per session scan A 88076f439db0
solana-qa-engineer is an agent published in the GitHub repository GeckoVision/gecko-surf (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 1,764 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to solana-qa-engineer, differing in 3 lines, and is treated as a copy.
Other agents, from other repositories
writ-test-writer
Writes test skeleton files with method signatures and assertions based on an approved plan. Use after plan approval, before implementation.
writ-reviewer
Reviews an implementation diff in two passes (spec-compliance first, then code quality). Read-only. Returns structured findings. Replaces the separate spec/code-quality reviewers.
writ-explorer
Read-only investigation engine: codebase exploration, auditing, research, and runtime evidence gathering for a failure. Cannot modify files. Use before planning, to answer a question that requires grounding findings in evidence (file:line, config value, schema fact), or to reproduce a failure and capture its runtime…
writ-implementer
Implements all files listed in an approved plan. Writes production code, configuration, and updates test implementations. Use after test skeleton approval.
writ-planner
Designs implementation plans for coding tasks. Writes plan.md and capabilities.md to the project root. Use after exploration, before test writing.
test-mapper
Wave 3 agent: documents testing patterns, test organization, coverage gaps, and testing conventions across the codebase. Links test memories with EXPLAINS, EXEMPLIFIES, DEPENDSON, and SIMILARTO relationships.