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/mystenlabs/sui/simtest-debugnpx skills add MystenLabs/sui --skill simtest-debuggit clone --depth 1 https://github.com/MystenLabs/suiWhat 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.00025 | $0.01316 |
| Opus 5 | $0.00013 | $0.00658 |
| Sonnet 5 | $0.00005 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
simtest-debug 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug a simtest failure
Debugs a simtest failure using logging and the scientific method.
Usage
/debug-simtest <repro command or test>
Example: /debug-simtest MSIM_TEST_SEED=1768248386016 RUST_LOG=sui=debug,info cargo simtest --test address_balance_tests test_deposit_and_withdraw
Example: `/debug-simtest test_deposit_and_withdraw
Arguments
$ARGUMENTS should contain either:
- a command to run to reproduce the test failure
- the name of a test
Instructions
This skill logs its progress to a file called NOTEBOOK.md in the repo root. The file should look like
# iteration 1
- OBSERVATIONS
- <observation 1>
- <observation 2>
- ...
- HYPOTHESIS: <description of hypothesis>
- EXPERIMENT: <description of experiment>
- RESULTS: <did the experiment confirm or refute the hypothesis?>
# iteration 2
<more observations, hypothesis, etc>
While executing the skill, never make functional changes to the code. Only add logging statements as described below. The goal is to find the root cause, not fix the issue. If at any point the reproduction command stops failing, or fails in a different way, this indicates that functional changes have been made. The test is deterministic and cannot be affected by emitting logs, doing expensive computations, etc.
Log File Management
Log files should be named consistently using the experiment number: experiment_N.log (e.g., experiment_1.log, experiment_2.log, etc.).
- Never delete log files during the debugging session - the user will clean them up when debugging is complete.
- Do not commit log files to git - they are too large.
Commit Strategy
After each experiment:
- Commit only the logging changes (code modifications) with a message indicating the experiment number:
CLAUDE: experiment N logging - Make a separate commit for NOTEBOOK.md updates with a message like
CLAUDE: experiment N observations
This keeps the debugging history clean and allows easy navigation between experiments. Do not include log files in any commits.
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 · 118 lines · 25 tokens per session scan A c1556712e13c
simtest-debug is a skill published in the GitHub repository MystenLabs/sui (7,741 stars, last pushed 2d ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,316 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-30.
Other skills, from other repositories
squash-bugbot
Triage unresolved bot review comments on a GitHub PR. Use when asked to run /squash-bugbot or to assess, fix, dismiss, reply to, or resolve bot review feedback.
developing-smart-contracts
Solidity smart contract development guidelines for Lineth blockchain. Use when writing, reviewing, or refactoring Solidity contracts, or when the user asks about Solidity best practices, contract structure, or NatSpec docstrings. Covers NatSpec documentation, naming conventions, file layout, and code style.
lineth-quickstart
Operating manual for the Lineth Stack quickstart — the Docker-Compose dev/demo stack at docs/getting-started/lineth-stack in the lineth-monorepo that boots a local Linea/Lineth L2 with Sepolia or local L1 finality. Use whenever you are working inside the lineth-stack quickstart and need to boot or run the stack…
frontend-design
Create distinctive, production-grade Stellar dApp UI. Combines bold aesthetic direction with smart contract integration patterns — wallet connection flows, transaction UX, contract data displays, and agentic kit hook wiring. No generic "AI slop" aesthetics.
stellar-mcp
MCP (Model Context Protocol) tools for Stellar development. Gives Claude direct access to the Stellar blockchain, filesystem, GitHub, and Playwright through configured MCP servers. Use when querying chain data, deploying contracts, managing repos, or running e2e tests from within the agent.
klever-dev
End-to-end Klever blockchain development — smart contracts (Rust/WASM), transaction building (@klever/connect, klever-go-sdk), deployment via ksc + koperator, and on-chain interaction via MCP tools. Use when the task involves KLV, KDA tokens, klv1 addresses, Klever smart contracts, or Klever node/API interaction.