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.
npx agentmods add commands/0x-j/sui-stack-claude-code-plugin/test-movegit clone --depth 1 https://github.com/0x-j/sui-stack-claude-code-pluginWhat 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 | $0.00016 | $0.02021 |
| Opus 5 | $0.00008 | $0.01010 |
| Sonnet 5 | $0.00003 | $0.00404 |
| Haiku 4.5 | $0.00002 | $0.00202 |
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.
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
- Locates Move package
- Parses command arguments for filters and options
- Runs
sui move testwith appropriate flags - Formats and presents results
- 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:
--coverageor-c: Enable coverage reporting--gas-profileor-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 testsui 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
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.
- 2d ago First seen · 412 lines · 16 tokens per session scan A 4b6826ebe0dc
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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.