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.
curl -O https://raw.githubusercontent.com/solanabr/solana-vault-standard/main/.claude/commands/benchmark.mdgit clone --depth 1 https://github.com/solanabr/solana-vault-standardWrote 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-vault-standard/benchmark)<a href="https://agentmods.dev/commands/solanabr/solana-vault-standard/benchmark"><img src="https://agentmods.dev/badge/commands/solanabr/solana-vault-standard/benchmark.svg" alt="Measured on agentmods" 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.00010 | $0.01554 |
| Opus 5 | $0.00005 | $0.00777 |
| Sonnet 5 | $0.00002 | $0.00311 |
| Haiku 4.5 | $0.00001 | $0.00155 |
Grade A, and why
benchmark 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.
This is a copy
100% identical to benchmark — 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.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running CU benchmarks for a Solana program and comparing results against a stored baseline. This detects performance regressions and tracks optimization progress.
Related Skills
- ext/solana-dev/skill/references/programs/pinocchio.md - CU optimization techniques
- ext/solana-dev/skill/references/testing.md - Test framework CU measurement
Step 1: Setup
BENCHMARK_DIR=".claude/benchmarks"
BASELINE_FILE="$BENCHMARK_DIR/cu-baseline.json"
CURRENT_FILE="$BENCHMARK_DIR/cu-current.json"
mkdir -p "$BENCHMARK_DIR"
echo "Benchmark configuration:"
echo " Baseline: $BASELINE_FILE"
echo " Output: $CURRENT_FILE"
echo ""
# Verify project
if [ ! -f "Anchor.toml" ] && [ ! -f "Cargo.toml" ]; then
echo "No Anchor.toml or Cargo.toml found. Cannot benchmark."
exit 1
fi
Step 2: Build Program
echo "Building program..."
if [ -f "Anchor.toml" ]; then
anchor build
else
cargo build-sbf
fi
if [ $? -ne 0 ]; then
echo "Build failed. Fix compilation errors before benchmarking."
exit 1
fi
echo "Build successful."
echo ""
Step 3: Run Tests with CU Measurement
echo "Running test suite with CU measurement..."
echo ""
export SBF_OUT_DIR=target/deploy
if [ -f "Anchor.toml" ]; then
# Run Anchor tests, capture CU output
anchor test --skip-deploy 2>&1 | tee /tmp/benchmark-output.txt
else
cargo test 2>&1 | tee /tmp/benchmark-output.txt
fi
TEST_STATUS=$?
if [ $TEST_STATUS -ne 0 ]; then
echo ""
echo "Tests failed. Fix failures before benchmarking."
exit 1
fi
echo ""
echo "Tests passed. Parsing CU data..."
Step 4: Parse CU Results
Extract CU consumption per instruction from test output.
echo "Parsing CU usage from test output..."
# Extract lines with CU data
# Pattern: "Program <ID> consumed <N> of <M> compute units"
grep -i "consumed.*compute units" /tmp/benchmark-output.txt > /tmp/cu-lines.txt
TOTAL_INSTRUCTIONS=$(wc -l < /tmp/cu-lines.txt)
echo "Found $TOTAL_INSTRUCTIONS instruction CU measurements."
echo ""
# Display raw CU data
echo "Raw CU measurements:"
cat /tmp/cu-lines.txt
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 · 228 lines · 10 tokens per session scan A ed099fa97974
benchmark is a command published in the GitHub repository solanabr/solana-vault-standard (23 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 1,554 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to benchmark, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.
design-benchmark
Design a benchmark suite to measure AI product performance over time.