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/commands/solanabr/solana-ai-kit/test-rust)<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/test-rust"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/test-rust/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/commands/solanabr/solana-ai-kit/test-rust"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/test-rust.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.00022 | $0.01085 |
| Opus 5.5 | $0.00009 | $0.00434 |
| Sonnet 5.5 | $0.00004 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade C, and why
test-rust scanned grade C with 2 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 25d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- Surfpool, for mainnet-fork state and cheatcodes: `NO_DNA=1 surfpool start` and point tests at `http://127.0.0.1:8899`, or embed `surfpool-sdk` so each suite owns its surfnet. Install with `curl -sL https://run.surfpool Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Surfpool, for mainnet-fork state and cheatcodes: `NO_DNA=1 surfpool start` and point tests at `http://127.0.0.1:8899`, or embed `surfpool-sdk` so each suite owns its surfnet. Install with `curl -sL https://run.surfpool How it starts
The opening of the file, as written. The whole thing — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the project's Rust test suites and report each failure with its cause. $ARGUMENTS narrows the run (a package, test name, or filter passed to cargo test); empty means everything.
Harness setup and patterns: testing.md. Surfpool flags and cheatcodes: surfpool/overview.md.
Steps
- Rebuild the program before running program tests:
NO_DNA=1 anchor buildorcargo build-sbf. LiteSVM and Mollusk loadtarget/deploy/<name>.so(the Anchor LiteSVM templateinclude_bytes!s it at compile time), socargo testalone tests whatever binary was built last.NO_DNA=1turns off Anchor and Surfpool prompts and TUIs for agent runs. - Run the suite that fits:
- Anchor 1.x:
anchor initscaffolds Rust LiteSVM tests inprograms/<name>/tests/with[scripts] test = "cargo test".NO_DNA=1 anchor testbuilds, starts Surfpool, deploys, runs that script, and streams program logs to.anchor/program-logs/. In-process suites need no validator:anchor test --skip-local-validator --skip-deploy(neweranchor initwritesskip_local_validator = truefor you), orcargo test -p <name>after step 1. - Native or Pinocchio:
cargo test-sbfbuilds the program and setsSBF_OUT_DIR, whereMollusk::new(&id, "<name>")finds<name>.so(it also searchestests/fixturesand the cwd). - Mollusk, for single-instruction and CU tests:
Check::compute_units(n)expects exactly n, so assert a ceiling onresult.compute_units_consumedyourself.MolluskComputeUnitBencher(run throughcargo bench) writescompute_units.mdwith deltas. - Surfpool, for mainnet-fork state and cheatcodes:
NO_DNA=1 surfpool startand point tests athttp://127.0.0.1:8899, or embedsurfpool-sdkso each suite owns its surfnet. Install withcurl -sL https://run.surfpool.run/ | bash; thesurfpoolcrate on crates.io is an unrelated package. - Fuzzing: Trident (
trident initonce, thentrident fuzz run fuzz_0), oranchor fuzz(Crucible) on Anchor 1.2+. Give runs minutes to hours and assert invariants such as value conservation, not only "no panic". - Rust backends:
cargo test --workspace; add-- --test-threads=1when tests share a database, and setDATABASE_URLfor#[sqlx::test].
- Anchor 1.x:
- Rerun only the failures:
cargo test <name> -- --exact --nocapture.
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.
- 25d ago Changed · -372 lines · +12 tokens per session scan A → C 6e5b58e7dff6
- 26d ago Changed 5813bc3f77ca
- 1mo ago First seen · 404 lines · 10 tokens per session scan A 3930d45f8cfe
test-rust is a command published in the GitHub repository solanabr/solana-ai-kit (104 stars, last pushed 26d ago), licensed MIT. It adds 22 tokens to every session and 1,085 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
cargo-test
Command "cargo-test" from olorehq/olore, covering cargo-test(1), name, synopsis, description and documentation tests.
cargo-miri
Command "cargo-miri" from olorehq/olore, covering cargo-miri(1), name, description and see also.
benchmark
Design and coordinate a reproducible Java performance test.
apex
APEX Methodology - The systematic Analyze-Plan-Execute-eLicit-eXamine approach for intelligent development. Reduces hallucination and defect risk through mandatory parallel research, self-review, and validation gates.
plan-feature
Production-grade feature planning with dual-AI validation (Claude + Antigravity/Gemini 3 via agy).
generate-tests
Begin by outputting: [ Manta — Generate Tests ].