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 simiancraft/simiancraft-skills --skill ios-simulator-flow-evidencegit clone --depth 1 https://github.com/simiancraft/simiancraft-skillsWrote 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/simiancraft/simiancraft-skills/ios-simulator-flow-evidence)<a href="https://agentmods.dev/skills/simiancraft/simiancraft-skills/ios-simulator-flow-evidence"><img src="https://agentmods.dev/badge/skills/simiancraft/simiancraft-skills/ios-simulator-flow-evidence/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/simiancraft/simiancraft-skills/ios-simulator-flow-evidence"><img src="https://agentmods.dev/badge/skills/simiancraft/simiancraft-skills/ios-simulator-flow-evidence.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00118 | $0.00873 |
| Opus 5 | $0.00059 | $0.00436 |
| Sonnet 5 | $0.00024 | $0.00175 |
| Haiku 4.5 | $0.00012 | $0.00087 |
Grade A, and why
ios-simulator-flow-evidence 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Simulator Flow Evidence (extraction, not publishing)
Owns getting artifacts OUT of the simulator. The separate prove-work-on-github
skill consumes them; the seam is references/artifact-contract.md. This skill
produces the bundle; it does not publish it.
The three artifact kinds
A driven flow (see ios-simulator references/driving.md) leaves three kinds of proof:
- A sequence of screenshots (
references/screenshots.md): one PNG per meaningful step, each vision-verified to show the state it claims. The default, most reviewable evidence. - A video (
references/video.md): the whole flow as one MP4 or MOV. An animated GIF is not a native output; it is a post-process that needs a separate tool (see that file). - A manifest (
references/flow-manifest.md): a machine-readable index tying each step to its artifact and the state it proves, so a reviewer (or the presentation skill) can read the bundle without re-running the flow.
All capture comes from the device framebuffer, so the Simulator window's size and position
never matter (see ios-simulator references/capture.md); never resize or full-screen it.
The contract
Everything this skill emits conforms to references/artifact-contract.md: stable names,
known formats (PNG, MP4 or MOV), and the manifest shape. The consumer prove-work-on-github
relies on that contract; do not break it without updating the presentation side.
Honest can't-do list (simulator limits)
Evidence from a simulator proves UI, navigation, wiring, and state, not device fidelity. A simulator cannot:
- vend a native APNs device token (
getDevicePushTokenAsync), so real remote-push registration is a device pass; a simulator can still display a payload viaxcrun simctl pushand receive a remote push on Xcode 14+ (see expo-ios-simulatorreferences/known-prompts.mdfor the push-token alert this raises); - produce real camera or microphone frames (no physical sensors);
- place a phone call or send a carrier SMS;
- fully reproduce on-device network conditions (no cellular radio; bandwidth and latency are the host's, not a real handset's).
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 · 73 lines · 118 tokens per session scan A 9fbd79d6a8fe
ios-simulator-flow-evidence is a skill published in the GitHub repository simiancraft/simiancraft-skills (7 stars, last pushed 7d ago), licensed MIT. It adds 118 tokens to every session and 873 once invoked, about $0.0006 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-31.
Other skills, from other repositories
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…
ios-device-qa
Use when the user runs /ios-device-qa to drive a real iPhone over USB through a debug-bridge daemon and return a device QA report with verified interactions. Do not use for remote, credential, publish, deploy, or irreversible changes.
xcode-simulator-testing
Use when asked to run /xcode-simulator-testing with a scheme name or current to build and launch an iOS app in a simulator. Not for project regeneration: use ios-build-fix.
mobile-app-testing
Record real-device (iOS Simulator / Android emulator) test flows for your app (web or native) via tapflow's MCP server, replay them with tapflow's own CLI, and stream results into an installed e2e-dashboard.
xcode-testing-workflow
Guide Swift Testing, XCTest, XCUITest, XCUIAutomation-oriented mechanics, code coverage, xctestplan matrices, accessibility-verification follow-through, test filtering, retries, diagnostics, and test-specific fallback work in existing Xcode-managed projects and workspaces. Use when Xcode-aware execution is needed and…
maestro-fix-cycle
Auto-repair loop for failing Maestro mobile tests on the iOS Simulator, one flow at a time. Use when you want mobile/simulator tests fixed automatically. Triggers on: conserta os testes mobile, arruma o teste do simulador, loop de correcao mobile, fix mobile tests, auto fix ios tests.