test-move

A command for running tests for Sui Move packages. Move is a programming language used for smart contracts, and Sui is a blockchain platform that runs them.

In plain words
What is it for?
Use it to run all Move tests or filter by test name or module, with optional code-coverage and gas-profiling reports.
Why use it?
It avoids manually locating the package and assembling test options when you need focused tests, coverage data, or gas-use analysis.

Command

Install

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.

agentmods
npx agentmods add commands/0x-j/sui-stack-claude-code-plugin/test-move
Clone the repo
git clone --depth 1 https://github.com/0x-j/sui-stack-claude-code-plugin
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,021 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00016 $0.02021
Opus 5 $0.00008 $0.01010
Sonnet 5 $0.00003 $0.00404
Haiku 4.5 $0.00002 $0.00202

Measured 2d ago against content hash 4b6826ebe0dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-move 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 2d 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.

commands/test-move.md · 412 lines

How it starts

The opening of the file, as written. The whole thing — 412 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Move Contracts

Run Move test suite with options for filtering specific tests, coverage analysis, and gas profiling. Provides formatted output and actionable insights.

What This Command Does

  1. Locates Move package
  2. Parses command arguments for filters and options
  3. Runs sui move test with appropriate flags
  4. Formats and presents results
  5. Provides coverage or gas analysis if requested

Instructions

Step 1: Locate Package

Check for Move.toml:

# Current directory
if [ -f "Move.toml" ]; then
  PACKAGE_PATH="."
# Or find in subdirectories
else
  find . -name "Move.toml" -maxdepth 3
fi

If multiple packages found, ask user which to test.

Step 2: Parse Arguments

Extract from arguments:

Test filter (optional):

  • Specific test function name
  • Module name pattern
  • Example: test_create, my_module::test_*

Flags:

  • --coverage or -c: Enable coverage reporting
  • --gas-profile or -g: Enable gas profiling
  • Both can be combined

Step 3: Run Basic Tests

Without filter:

cd [PACKAGE_PATH]
sui move test

With filter:

sui move test [FILTER]

Examples:

  • sui move test test_create_nft - Run specific test
  • sui move test my_module - Run all tests in module

Step 4: Format Test Results

Parse output for:

  • Total tests run
  • Passed tests
  • Failed tests
  • Test names and durations

Present formatted summary:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🧪 Test Results
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Total Tests:    15
Passed:         14 ✓
Failed:         1 ✗
Duration:       2.3s

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

If all tests pass:

✅ All tests passed!

If tests fail:

❌ Tests failed

Failed:
  • test_invalid_input (my_module)
    Expected: 0, Got: 1

Review failures and fix before deploying.

Step 5: Coverage Analysis

If --coverage flag provided:

sui move test --coverage

Parse coverage output:

  • Lines covered/total
  • Coverage percentage by module
  • Uncovered lines

Read the full file on GitHub · 412 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. 2d ago First seen · 412 lines · 16 tokens per session scan A 4b6826ebe0dc

Subscribe to this mod's changes

test-move is a command published in the GitHub repository 0x-j/sui-stack-claude-code-plugin (10 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 2,021 once invoked, about $0.0001 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-08-31.