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 skills add swesmith/davila7__claude-code-templates.734b8a50 --skill move-code-qualitygit clone --depth 1 https://github.com/swesmith/davila7__claude-code-templates.734b8a50Wrote 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/swesmith/davila7__claude-code-templates.734b8a50/move-code-quality)<a href="https://agentmods.dev/skills/swesmith/davila7__claude-code-templates.734b8a50/move-code-quality"><img src="https://agentmods.dev/badge/skills/swesmith/davila7__claude-code-templates.734b8a50/move-code-quality/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/swesmith/davila7__claude-code-templates.734b8a50/move-code-quality"><img src="https://agentmods.dev/badge/skills/swesmith/davila7__claude-code-templates.734b8a50/move-code-quality.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.00057 | $0.03451 |
| Opus 5.5 | $0.00023 | $0.01380 |
| Sonnet 5.5 | $0.00011 | $0.00690 |
| Haiku 4.5 | $0.00006 | $0.00345 |
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 1mo 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 move-code-quality — 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Move Code Quality Checker
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 50+ 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
Implicit Framework Dependency
- ✅ For Sui 1.45+: No explicit
Sui,Bridge,MoveStdlib,SuiSystemin[dependencies] - ❌ OUTDATED: Explicit framework dependencies listed
Prefix Named Addresses
- ✅ GOOD:
my_protocol_math = "0x0"(project-specific prefix) - ❌ BAD:
math = "0x0"(generic, conflict-prone)
3. Imports, Modules & Constants
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.
- 1mo ago First seen · 416 lines · 57 tokens per session scan A 3bcc527a435b
move-code-quality is a skill published in the GitHub repository swesmith/davila7__claude-code-templates.734b8a50 (2 stars, last pushed 10mo ago), licensed MIT. It adds 57 tokens to every session and 3,451 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to move-code-quality, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…