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 holon-run/uxc --skill sui-jsonrpc-skillgit clone --depth 1 https://github.com/holon-run/uxcWrote 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/holon-run/uxc/sui-jsonrpc-skill)<a href="https://agentmods.dev/skills/holon-run/uxc/sui-jsonrpc-skill"><img src="https://agentmods.dev/badge/skills/holon-run/uxc/sui-jsonrpc-skill/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/holon-run/uxc/sui-jsonrpc-skill"><img src="https://agentmods.dev/badge/skills/holon-run/uxc/sui-jsonrpc-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.01120 |
| Opus 5 | $0.00020 | $0.00560 |
| Sonnet 5 | $0.00008 | $0.00224 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
sui-jsonrpc-skill 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 9d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sui JSON-RPC Skill
Use this skill to run Sui JSON-RPC operations through uxc + JSON-RPC.
Reuse the uxc skill for shared execution and error-handling guidance.
Prerequisites
uxcis installed and available inPATH.- Network access to
https://fullnode.mainnet.sui.io. - No API key is required for the public mainnet fullnode in this skill's default flow.
Scope
This skill covers a safe read-first Sui JSON-RPC surface:
- chain identity and latest checkpoint reads
- checkpoint lookup
- object lookup
- reference gas price reads
- latest system state reads
- pubsub subscriptions for events and transaction effects
This skill does not cover:
unsafe_*transaction-building methodssui_executeTransactionBlock- wallet signing flows
- custom/private Sui RPC providers with different auth or rate limits
Endpoint And Discovery
This skill targets the public Sui fullnode endpoint:
https://fullnode.mainnet.sui.io
For pubsub, use a Sui provider WebSocket endpoint that you have verified actually accepts JSON-RPC subscriptions. Do not assume the public HTTPS fullnode host automatically supports the same wss:// hostname for pubsub.
uxc JSON-RPC discovery depends on OpenRPC or rpc.discover. Sui exposes a discoverable method surface, so help-first flow works directly against the endpoint.
Authentication
The default public endpoint used by this skill does not require authentication.
If a user later points the same workflow at a private Sui RPC provider, verify its auth model first before reusing this skill unchanged.
Core Workflow
-
Use the fixed link command by default:
command -v sui-jsonrpc-cli- If missing, create it:
uxc link sui-jsonrpc-cli https://fullnode.mainnet.sui.io sui-jsonrpc-cli -h
-
Inspect operation schema first:
sui-jsonrpc-cli sui_getLatestCheckpointSequenceNumber -hsui-jsonrpc-cli sui_getCheckpoint -hsui-jsonrpc-cli sui_getObject -h
-
Prefer read/setup validation before any deeper query:
sui-jsonrpc-cli sui_getChainIdentifiersui-jsonrpc-cli sui_getLatestCheckpointSequenceNumbersui-jsonrpc-cli suix_getReferenceGasPrice
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 113 lines · 40 tokens per session scan A e90e5a7ee441
sui-jsonrpc-skill is a skill published in the GitHub repository holon-run/uxc (113 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,120 once invoked, about $0.0002 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
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…
linear
Linear project management — issues, cycles, and projects via GraphQL API.
cymbal
Tree-sitter indexed code navigator. Use the cymbal CLI — not Read, Grep, Glob, or Bash — for finding where symbols are defined, tracing callers and callees, locating interface implementations, understanding the impact of a change, and mapping imports across an existing codebase. Returns precise, token-efficient…
api-design-patterns
Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices.
pipefy-api-fallback
Use this skill when an MCP tool fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow the 3-tier…