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/simulator-controlnpx skills add dashpay/platform --skill simulator-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.07039 |
| Opus 5 | $0.00051 | $0.03520 |
| Sonnet 5 | $0.00020 | $0.01408 |
| Haiku 4.5 | $0.00010 | $0.00704 |
Grade A, and why
simulator-control scanned grade A with 2 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `curl` + `WebFetch` | builtin | Cross-check chain state via insight.testnet API | Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
subprocess.run( How it starts
The opening of the file, as written. The whole thing — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simulator Control — drive + inspect SwiftExampleApp
When the user is testing SwiftExampleApp in the iOS simulator, you can do everything they could do: tap buttons by label, type text, swipe, dump the accessibility tree, screenshot the screen, read the SwiftData store directly for ground truth, cross-check chain state against testnet. Use this together with the human-in-the-loop, not against them — confirm with them before destructive actions.
Required tooling
| Tool | Install | Why |
|---|---|---|
xcrun simctl |
Xcode CLT (already installed for iOS dev) | Screenshot, app container, openurl, logs |
sqlite3 |
macOS default | Read SwiftData default.store |
idb + idb_companion |
brew install facebook/fb/idb-companion + pipx install --python /opt/homebrew/bin/python3.12 fb-idb (fb-idb 1.1.7 uses asyncio.get_event_loop() which Python 3.14 dropped — must pin 3.12) |
Tap / swipe / type / accessibility tree |
curl + WebFetch |
builtin | Cross-check chain state via insight.testnet API |
Without idb the inspection workflows (screenshot + SwiftData + logs) still work; only control workflows are blocked.
Quick command reference
# === Setup (once per session) ===
export PATH="$HOME/.local/bin:$PATH"
UDID=$(xcrun simctl list devices booted | awk -F'[()]' '/Booted/ {print $2}')
idb connect $UDID # starts idb_companion alongside the running sim
BUNDLE=org.dashfoundation.DashDeveloperPro
# === INSPECT ===
xcrun simctl io booted screenshot /tmp/sim.png # screenshot
idb ui describe-all --udid $UDID # accessibility tree (JSON)
idb ui describe-point --udid $UDID X Y # element under coord
# === CONTROL ===
idb ui tap --udid $UDID X Y # tap at coord
idb ui swipe --udid $UDID X1 Y1 X2 Y2 --duration 0.3 # swipe
idb ui text --udid $UDID "hello" # type text into focused field
idb ui key --udid $UDID 40 # short press keycode (40 = return)
idb ui button --udid $UDID HOME # hardware buttons: HOME, LOCK, SIRI, SIDE_BUTTON
# === APP ===
xcrun simctl launch booted $BUNDLE
xcrun simctl terminate booted $BUNDLE
xcrun simctl openurl booted "dashplatform://identity/abc123"
# === DATA ===
DATA=$(xcrun simctl get_app_container booted $BUNDLE data)
STORE="$DATA/Library/Application Support/default.store"
sqlite3 "$STORE" "SELECT ..."
# === LOGS ===
xcrun simctl spawn booted log show --last 60s --info \
--predicate 'processImagePath CONTAINS "SwiftExampleApp"'
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 · 409 lines · 101 tokens per session scan A 3b1854b67297
simulator-control is a skill published in the GitHub repository dashpay/platform (92 stars, last pushed yesterday), licensed MIT. It adds 101 tokens to every session and 7,039 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). 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.