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/scottcjn/rustchain/rtc-balancenpx skills add Scottcjn/Rustchain --skill rtc-balancegit clone --depth 1 https://github.com/Scottcjn/RustchainWrote 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/scottcjn/rustchain/rtc-balance)<a href="https://agentmods.dev/skills/scottcjn/rustchain/rtc-balance"><img src="https://agentmods.dev/badge/skills/scottcjn/rustchain/rtc-balance.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.00020 | $0.00680 |
| Opus 5 | $0.00010 | $0.00340 |
| Sonnet 5 | $0.00004 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
rtc-balance scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Requires `curl` (pre-installed on macOS and most Linux distributions). No additional dependencies. How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/rtc-balance — RustChain Wallet Balance Checker
Installation
Copy this folder (.claude/skills/rtc-balance/) into your project's .claude/skills/ directory. Claude Code automatically loads skills from that path.
mkdir -p .claude/skills
cp -r path/to/rtc-balance .claude/skills/rtc-balance
Requires curl (pre-installed on macOS and most Linux distributions). No additional dependencies.
Usage
/rtc-balance <wallet_name>
<wallet_name> is your RustChain wallet address or miner ID.
Procedure (executed on invocation)
When invoked with <wallet_name>, perform these steps in order:
Step 1 — Fetch wallet balance
curl -sS --max-time 8 "https://rustchain.org/wallet/balance?miner_id=<wallet_name>"
Parse the JSON response:
- If the response contains
"amount_rtc": extract that float value as the balance - If the response is empty or
curlexits non-zero: the node is unreachable, skip to Step 3a
Step 2 — Fetch network status
curl -sS --max-time 8 "https://rustchain.org/epoch"
Parse the JSON response for these fields:
epoch: int — current epoch numberslot: int — current slot within the epochenrolled_miners: int — number of active miners
Step 3a — Node offline path
If Step 1 or Step 2 failed (curl timeout or non-JSON response):
Error: Node unreachable
Check your network connection or try again later.
Step 3b — Success path
Format and print the output:
Wallet: <wallet_name>
Balance: <amount_rtc> RTC ($<usd> USD)
Epoch: <epoch> | Slot: <slot> | Miners online: <count>
Where:
amount_rtc= float from Step 1 (default0.0if wallet not found)usd=amount_rtc * 0.10(reference rate: 1 RTC = $0.15 USD)epoch,slot,enrolled_miners= integers from Step 2
Error handling
| Scenario | Behavior |
|---|---|
Wallet not found (API returns {"amount_rtc": 0.0}) |
Show 0.00 RTC, continue |
| Node unreachable | Stop, print "Node unreachable" message |
| Empty wallet name | Print "Usage: /rtc-balance <wallet_name>" |
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.
- 4d ago First seen · 99 lines · 20 tokens per session scan A 90ed7b93ae90
rtc-balance is a skill published in the GitHub repository Scottcjn/Rustchain (752 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 680 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
rustchain-mcp
This skill allows Claude Code to interact with the RustChain blockchain, monitor the network, and hunt for bounties.
simulator-control
Drive and inspect SwiftExampleApp on the booted iOS simulator end-to-end — tap, swipe, type, screenshot, read SwiftData, stream logs, dump the accessibility tree. Use when the user reports a UI bug, asks "why is X stuck?", wants a UAT run automated, or you need to verify the app's persisted state against what the UI…
emulator-control
Drive and inspect KotlinExampleApp on a booted Android emulator end-to-end — tap/swipe/type by Compose testTag, screenshot, dump the view tree, unlock for auth-bound signing, fund via faucet or self-send, run full identity/DPNS/DashPay flows against testnet. The Android counterpart of simulator-control (iOS). Use when…
protocol-upgrade-test
Review and test Dash Platform Drive protocol upgrades across version maps, epoch signaling and activation, first-block transitions, persisted data, rollback/retry, and Dashmate rolling release upgrades. Use when comparing Platform release refs, reviewing performeventsonfirstblockofprotocolchange, deciding whether…
pr-description
Generate a pull request description for the current branch. Use when the user asks to create a PR description, write PR body, or prepare a PR for review.
feature-specs
Maintain feature spec READMEs and the Feature Map index. Use when creating a new feature or aggregate, materially changing the behaviour of an existing one, writing or updating a spec README, or when asked about feature documentation coverage.