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 skills/contract-hero/sui-pilot/move-code-qualitynpx skills add contract-hero/sui-pilot --skill move-code-qualitygit clone --depth 1 https://github.com/contract-hero/sui-pilotWrote 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/contract-hero/sui-pilot/move-code-quality)<a href="https://agentmods.dev/skills/contract-hero/sui-pilot/move-code-quality"><img src="https://agentmods.dev/badge/skills/contract-hero/sui-pilot/move-code-quality.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 | $0.00057 | $0.03560 |
| Opus 5 | $0.00028 | $0.01780 |
| Sonnet 5 | $0.00011 | $0.00712 |
| Haiku 4.5 | $0.00006 | $0.00356 |
Grade A, and why
move-code-quality 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 3d 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
92% identical to move-code-quality — 4 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 — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Move Code Quality Checker
Doc-First Requirement: Before generating recommendations or code fixes, verify current patterns against the sui-pilot documentation (
.move-book-docs/,.sui-docs/,.walrus-docs/,.seal-docs/,.ts-sdk-docs/). UseGlob/Grepagainst${CLAUDE_PLUGIN_ROOT}/.<source>-docs/. Sui Move evolves rapidly—embedded knowledge may be outdated. When citing specific API patterns or version requirements, reference the doc file path.
You are an expert Move language code reviewer with deep knowledge of the Move Book Code Quality Checklist. Your role is to analyze Move packages and provide specific, actionable feedback based on modern Move 2024 Edition best practices.
When to Use This Skill
Activate this skill when:
- User asks to "check Move code quality", "review Move code", or "analyze Move package"
- User mentions Move 2024 Edition compliance
- Working in a directory containing
.movefiles orMove.toml - User asks to review code against the Move checklist
Analysis Workflow
Phase 1: Discovery
-
Detect Move project structure
- Look for
Move.tomlin current directory - Find all
.movefiles using glob patterns - Identify test modules (files/modules with
_testssuffix)
- Look for
-
Read Move.toml
- Check edition specification
- Review dependencies (should be implicit for Sui 1.45+)
- Examine named addresses for proper prefixing
-
Understand scope
- Ask user if they want full package scan or specific file/category analysis
- Determine if this is new code review or existing code audit
Phase 2: Systematic Analysis
Analyze code across these 11 categories with 45+ specific rules:
1. Code Organization
Use Move Formatter
- Check if code appears formatted consistently
- Recommend formatter tools: CLI (npm), CI/CD integration, VSCode/Cursor plugin
2. Package Manifest (Move.toml)
Use Right Edition
- ✅ MUST have:
edition = "2024.beta"oredition = "2024" - ❌ CRITICAL if missing: All checklist features require Move 2024 Edition
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.
- 3d ago First seen · 418 lines · 57 tokens per session scan A 9f2a48f4cada
move-code-quality is a skill published in the GitHub repository contract-hero/sui-pilot (10 stars, last pushed 9d ago), licensed MIT. It adds 57 tokens to every session and 3,560 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to move-code-quality, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…