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/verifynpx skills add contract-hero/sui-pilot --skill verifygit 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/verify)<a href="https://agentmods.dev/skills/contract-hero/sui-pilot/verify"><img src="https://agentmods.dev/badge/skills/contract-hero/sui-pilot/verify.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.00214 | $0.03238 |
| Opus 5 | $0.00107 | $0.01619 |
| Sonnet 5 | $0.00043 | $0.00648 |
| Haiku 4.5 | $0.00021 | $0.00324 |
Grade A, and why
verify 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 5d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify — re-check Sui Move formal specifications against current code
Doc-First Requirement. The spec language is the Sui Prover's, not legacy MSL. When interpreting
prove_packagefindings, use the shared../specify/references/failure-taxonomy.mdand.sui-prover-docs/guide/spec-reference.md./verifyreads and re-proves specs — it never emits new spec syntax.
What /verify is (and is not)
/specify and /verify are the two halves of the FV workflow (design doc docs/specify-deliverable-design.html, Q4):
/specifyauthors. It writes#[spec(prove, target = …)]twins into a sibling<pkg>_specs/package and emits aspec-context.jsonmanifest binding each spec to the exact state it was proved against./verifychecks. It is read-mostly — it re-proves the existing specs against current source/deps/toolchain and reports drift. It writes only a report (and optionally refreshes drift badges in/specify's report). It never authors, edits, or deletes a spec.
A spec is a claim of the form "this code, at this state, against these deps, satisfies this property." /verify's job is to answer "is that claim still true, and is it still about the current code?" Those are two different questions — a spec can still pass yet no longer describe the code (source drifted), and a spec can fail on unchanged code (a real regression). /verify distinguishes them (Phase 4).
Inputs and modes
- Manifest-driven (full). When
spec-context.jsonexists (a package/specifyproduced),/verifydoes drift-aware verification: per-function source-hash comparison, dep/toolchain reproducibility checks, coverage drift, then re-prove. - Degraded (no manifest). When there is no
spec-context.json(hand-written specs, e.g.~/workspace/integer-library, or specs predating the manifest),/verifystill works: it discovers the spec package(s), re-proves them, and reports verdicts — but announces that drift detection is unavailable (no bound state to compare against) and suggests running/specifyonce to mint a manifest.
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.
- 5d ago First seen · 118 lines · 214 tokens per session scan A baa73a9f6969
verify is a skill published in the GitHub repository contract-hero/sui-pilot (10 stars, last pushed 4d ago), licensed MIT. It adds 214 tokens to every session and 3,238 once invoked, about $0.0011 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…