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/dashpay/platform/emulator-controlnpx skills add dashpay/platform --skill emulator-controlgit clone --depth 1 https://github.com/dashpay/platformWhat 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.00101 | $0.02678 |
| Opus 5 | $0.00051 | $0.01339 |
| Sonnet 5 | $0.00020 | $0.00536 |
| Haiku 4.5 | $0.00010 | $0.00268 |
Grade A, and why
emulator-control 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -s https://insight.testnet.networks.dash.org/insight-api/addr/<ADDR>` How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Emulator Control — drive + inspect KotlinExampleApp
The Android sibling of simulator-control. When testing KotlinExampleApp on an
Android emulator, you can do everything the user could: tap by Compose testTag,
type, swipe, screenshot, dump the view tree, unlock the device for auth-bound
signing, fund a wallet, and run identity/DPNS/DashPay flows against live
testnet. Use it alongside the human — confirm before spending funds or
broadcasting.
Setup (once per session)
export ANDROID_HOME=/opt/homebrew/share/android-commandlinetools
export PATH=$ANDROID_HOME/platform-tools:$PATH
export JAVA_HOME=/opt/homebrew/opt/openjdk@17 # for any gradle work
adb devices # find the running emulator
D=emulator-5554 # this session's serial
adb -s $D shell getprop ro.product.cpu.abi # MUST be arm64-v8a on Apple Silicon
PKG=org.dashfoundation.example # KotlinExampleApp
adb -s $D shell monkey -p $PKG -c android.intent.category.LAUNCHER 1 # launch
AVDs on this Mac: kotlin_sdk_ci (arm64-v8a — use this) and kotlin_sdk_ci_x86
(x86_64 — will NOT run the arm64-only native lib). API 35.
The killer feature: tap by Compose testTag
MainActivity sets Modifier.semantics { testTagsAsResourceId = true }, so every
Compose testTag shows up as resource-id in a uiautomator dump. That makes
the app fully scriptable by stable IDs — never hardcode pixel coords. The whole
driver is this helper (write it to the scratchpad once per session):
# ui.sh — dump the tree, find a node by resource-id (testTag) or text, tap center.
D=emulator-5554; X=/tmp/ui.xml
dump(){ adb -s $D shell uiautomator dump /sdcard/ui.xml >/dev/null 2>&1; adb -s $D pull /sdcard/ui.xml $X >/dev/null 2>&1; }
center_of(){ python3 - "$X" "$1" <<'PY'
import sys,re,xml.etree.ElementTree as ET
root=ET.parse(sys.argv[1]).getroot()
for n in root.iter('node'):
if n.get('resource-id','')==sys.argv[2]:
m=re.findall(r'\[(\d+),(\d+)\]\[(\d+),(\d+)\]',n.get('bounds',''))
if m: x1,y1,x2,y2=map(int,m[0]); print((x1+x2)//2,(y1+y2)//2); break
PY
}
tap_id(){ dump; read x y < <(center_of "$1"); [ -n "$x" ] && adb -s $D shell input tap $x $y || echo "NOT FOUND: $1"; }
shot(){ adb -s $D exec-out screencap -p > "/tmp/${1:-shot}.png"; }
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 · 185 lines · 101 tokens per session scan A d38664c4bc6b
emulator-control is a skill published in the GitHub repository dashpay/platform (92 stars, last pushed 2d ago), licensed MIT. It adds 101 tokens to every session and 2,678 once invoked, about $0.0005 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
rtc-balance
Check RustChain wallet balance, epoch info, and network status via the public RPC.
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.
dero
Query the DERO privacy blockchain and its documentation through the dero-mcp-server. Use for any DERO ecosystem question — node setup, smart contracts (DVM-BASIC), wallets, TELA apps, RPC methods, ports, privacy mechanics, transaction tracing, contract inspection.
local-network
Run isolated local Convex networks and in-process lattice node networks for development. Use when testing against local peers, reproducing peer or P2P replication issues, exercising NodeServer or P2PNode sync, or when no remote network is configured.
protocol-versions
Protocol versions, migrations and the v1 upgrade — which semantics to write against, and how to change CVM behaviour without forking the network. Use when changing core functions, juice costs, encodings or on-chain libraries.