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/protocol-confignpx skills add MystenLabs/sui --skill protocol-configgit 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.00028 | $0.01381 |
| Opus 5 | $0.00014 | $0.00691 |
| Sonnet 5 | $0.00006 | $0.00276 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
protocol-config 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 yesterday.
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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modify Protocol Config
Guides you through safely modifying the Sui protocol configuration, or verifies that existing changes were made correctly.
Usage
/protocol-config
When to Use
This skill serves two purposes:
-
Making changes - Use this skill to guide you through adding new features or modifying protocol config settings.
-
Verifying changes - Use this skill to check that protocol config changes already made in a branch are correct. This includes verifying that:
- A new protocol version was created if needed (not modifying a released version)
- The version history comment was added
- Chain-specific guards are used appropriately
- Snapshots were updated
When verifying existing work, follow steps 1-4 to confirm the changes are safe, then review the actual changes against the patterns in steps 5-7.
Background
The protocol config is defined in crates/sui-protocol-config/src/lib.rs. It controls blockchain behavior across all Sui networks. The critical constraint is:
Once a protocol version has been released to a production network, its settings CANNOT be changed.
This means if mainnet or testnet is running protocol version N, the settings for version N (and all prior versions) are frozen forever.
Instructions
1. Determine the most recently cut release branch
Find the latest release branch:
git fetch origin
git branch -r | grep 'origin/releases/sui-v' | grep -E '\-release$' | sort -V | tail -1
This returns something like origin/releases/sui-v1.66.0-release.
2. Check the max protocol version in the release branch
git show <release-branch>:crates/sui-protocol-config/src/lib.rs | grep 'const MAX_PROTOCOL_VERSION'
For example:
git show origin/releases/sui-v1.66.0-release:crates/sui-protocol-config/src/lib.rs | grep 'const MAX_PROTOCOL_VERSION'
3. Check the max protocol version in your feature branch
grep 'const MAX_PROTOCOL_VERSION' crates/sui-protocol-config/src/lib.rs
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.
- yesterday First seen · 176 lines · 28 tokens per session scan A 9123f1ef224e
protocol-config is a skill published in the GitHub repository MystenLabs/sui (7,741 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 1,381 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.