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 near-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/near-jsonrpc-skill)<a href="https://agentmods.dev/skills/holon-run/uxc/near-jsonrpc-skill"><img src="https://agentmods.dev/badge/skills/holon-run/uxc/near-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/near-jsonrpc-skill"><img src="https://agentmods.dev/badge/skills/holon-run/uxc/near-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.00033 | $0.01227 |
| Opus 5 | $0.00016 | $0.00613 |
| Sonnet 5 | $0.00007 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
near-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 11d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NEAR JSON-RPC Skill
Use this skill to run NEAR 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 a working NEAR RPC provider.
- This skill defaults to
https://free.rpc.fastnear.com, which is listed on the official NEAR RPC providers page. - Access to the curated NEAR OpenRPC schema URL:
https://raw.githubusercontent.com/holon-run/uxc/main/skills/near-jsonrpc-skill/references/near-public.openrpc.json
Scope
This skill covers a safe read-first NEAR RPC surface:
- chain status
- account state query
- finalized block lookup
- chunk lookup by chunk hash
- gas price lookup
- validator set lookup
This skill does not cover:
- transaction submission methods
- signing or wallet flows
- archival assumptions for very old blocks or chunks
- deprecated
near.orgorpagoda.copublic RPC endpoints
Endpoint And Schema
This skill uses the public FastNear mainnet RPC by default:
https://free.rpc.fastnear.com
The operation surface comes from the curated NEAR OpenRPC schema in this repo:
https://raw.githubusercontent.com/holon-run/uxc/main/skills/near-jsonrpc-skill/references/near-public.openrpc.json
uxc JSON-RPC discovery depends on OpenRPC or rpc.discover. FastNear does not expose a discoverable method surface that UXC can consume directly, so this skill uses a fixed --schema-url link and request flow.
The official NEAR docs now treat near.org and pagoda.co RPC endpoints as deprecated. Do not use those old hosts as the default for new automation.
If the user already has a preferred provider from the official NEAR providers page, relink the same command to that provider instead of reusing the deprecated endpoints.
Authentication
The default FastNear public RPC used by this skill does not require authentication.
If the user switches to a private NEAR provider, verify its auth model before reusing this skill unchanged.
What ships with it
4 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.
- 11d ago First seen · 114 lines · 33 tokens per session scan A e8da7d5f9187
near-jsonrpc-skill is a skill published in the GitHub repository holon-run/uxc (113 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,227 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…