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/x402agent/solana-clawdnpx agentmods add skills/x402agent/solana-clawd/pump-testingWrote 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/skills/x402agent/solana-clawd/pump-testing)<a href="https://agentmods.dev/skills/x402agent/solana-clawd/pump-testing"><img src="https://agentmods.dev/badge/skills/x402agent/solana-clawd/pump-testing/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/skills/x402agent/solana-clawd/pump-testing"><img src="https://agentmods.dev/badge/skills/x402agent/solana-clawd/pump-testing.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.00043 | $0.00646 |
| Opus 5 | $0.00022 | $0.00323 |
| Sonnet 5 | $0.00009 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
pump-testing 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 7d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing & Quality — Multi-Language Test Infrastructure
Comprehensive test infrastructure spanning Rust, TypeScript, Python, and Bash with CI quality gates.
Test Matrix
| Language | Framework | Directory | Focus |
|---|---|---|---|
| Rust | cargo test |
rust/tests/ |
Unit, integration, security |
| Rust | Criterion | rust/benches/ |
Performance benchmarks |
| TypeScript | Jest | typescript/tests/ |
Unit, integration |
| TypeScript | Jest | tests/ |
SDK tests |
| Python | Custom | tests/fuzz/ |
Fuzzing |
| Bash | Custom | tests/cli/ |
CLI integration |
Running Tests
# Rust
cargo test # All tests
cargo test --test integration_tests # Integration only
cargo test --test security_tests # Security only
cargo test --test performance_tests # Performance only
cargo bench # Criterion benchmarks
# TypeScript
npx jest # All Jest tests
npx jest --coverage # With coverage
# Shell
bash scripts/test-rust.sh # Full Rust test orchestration
bash docs/run-all-tests.sh # Run everything
Test Orchestration (test-rust.sh — 10 Steps)
- Check Rust toolchain
- Run
cargo fmt --check - Run
cargo clippy - Run unit tests
- Run integration tests
- Run security tests
- Run performance tests
- Run benchmarks
- Build release binary
- Verify binary output
Quality Gates
| Gate | Threshold |
|---|---|
| Rust tests | All pass |
| TypeScript tests | All pass |
cargo clippy |
No warnings |
cargo fmt |
Formatted |
| Coverage | >70% |
Stress / Benchmark Tests
# Rust benchmarks
cargo bench --bench generation_bench
# Stress tests
tests/stress/ # Long-running stability tests
tests/benchmarks/ # SDK benchmark tests
Patterns to Follow
- Write tests alongside implementation — not as an afterthought
- Test edge cases: zero amounts, null accounts, maximum values
- Test roundtrip consistency: buy→sell should approximate original (minus fees)
- Use transaction simulation for on-chain behavior verification
- Mock Anchor programs for offline SDK tests
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.
- 7d ago First seen · 92 lines · 43 tokens per session scan A 5f80feb9b0fb
pump-testing is a skill published in the GitHub repository x402agent/solana-clawd (24 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 646 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
tevm
Build, simulate, test, fork, and debug EVM transactions in TypeScript with tevm 1.0.0-rc.151. Use for in-process EVM scripts, typed Solidity imports, lazy mainnet or OP-stack forks, direct account and storage setup, viem-compatible contract actions, Vitest EVM tests, traces, and transaction simulation.
verification-protocol
How to prove a hypothesis is TRUE or FALSE using Move unit tests.
test-fixtures
Use when setting up test environments for Solidity protocols. Covers mock contracts, fork-based fixtures, shared setUp, factory patterns, token deployments, and reusable test helpers.
coverage-analysis
Use when measuring test coverage for Solidity contracts, identifying untested code paths, or establishing coverage requirements. Covers forge coverage, lcov output, visualization, and coverage-driven testing.
smart-contract-testing
Guide for testing smart contracts using Foundry and Hardhat, covering unit tests, fuzz testing, invariant testing, fork testing, and gas benchmarking.