lycorp-jp/sim-use is a command-line tool that lets AI agents observe and control iOS simulators, Android emulators, and devices through accessibility information and input actions. It helps agents test mobile applications by reading compact screen descriptions and interacting with named elements, while the catalogue skills and instructions teach agents how to use those capabilities.
Borrowing it
Nothing to install: this file belongs to lycorp-jp/sim-use. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lycorp-jp/sim-use/main/.agents/skills/release/SKILL.mdgit clone --depth 1 https://github.com/lycorp-jp/sim-useWrote 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/lycorp-jp/sim-use/release)<a href="https://agentmods.dev/skills/lycorp-jp/sim-use/release"><img src="https://agentmods.dev/badge/skills/lycorp-jp/sim-use/release/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/lycorp-jp/sim-use/release"><img src="https://agentmods.dev/badge/skills/lycorp-jp/sim-use/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 42 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- low Excessive Agency · line 6 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00061 | $0.02100 |
| Opus 5.5 | $0.00024 | $0.00840 |
| Sonnet 5.5 | $0.00012 | $0.00420 |
| Haiku 4.5 | $0.00006 | $0.00210 |
Grade A, and why
release 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 16d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill ships a new version of sim-use. The human types /release and you handle everything: version, CHANGELOG, one confirmation, then drive every command through to the homebrew-tap commit.
Run from the sim-use repo root (git rev-parse --show-toplevel).
The build/sign/tarball/formula logic lives in scripts/local-release.sh. Do not duplicate it. Your job is orchestration: state checks, version arithmetic, CHANGELOG rendering, user confirmation, git/tap operations, error recovery.
Step 1: Pre-flight
Run these checks. Abort with a clear error if any fails.
- Current branch is
main. - Working tree is clean (
git status --porcelainreturns nothing). - Local main is in sync with origin (
git fetch origin mainthen compare HEADs). If local is ahead, ask to push first; if behind, abort. gh auth statussucceeds (github.com).build_products/Frameworks/exists. If missing, runscripts/build.sh devto build them.- The homebrew-tap clone exists at
../lycorp-jp-homebrew-tap. If missing:
If it exists, verify it's clean and pull latest.git clone [email protected]:lycorp-jp/homebrew-tap.git ../lycorp-jp-homebrew-tap - Android bridge toolchain:
scripts/build-bridge.sh --checksucceeds. 7.5. E2E confidence suites are green (seedocs/ai/003-e2e-confidence-suite/):
(make e2e # iOS + Android scripted E2E vs Playground, in sequencemake e2e-ios/make e2e-androidrun one platform each.) A full green iOS pass alone is ~15 min, so budget ~20+ min. It prints a full pass/fail map and keeps going past failures. Any red suite blocks the release unless the user explicitly waives it at Step 3. Optional but recommended when skill prose changed this release (realclaude -pcost):make eval ARGS="-y -t quick"— the/run-evalsskill covers environment prep (Device Hub closed, fixtures installed) and pinning which sim-use binary is under test. - Signing + notarization readiness:
If either fails, surface the gap at Step 3 — don't silently switch to ad-hoc.security find-identity -v -p codesigning | grep -F "NAVER Japan K.K. (GFPYJQXRSN)" xcrun notarytool history --keychain-profile sim-use-notary >/dev/null 2>&1
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.
- 16d ago Changed · +4 lines f08298873fa6
- 23d ago Changed 2196c4435666
- 2mo ago First seen · 153 lines · 61 tokens per session scan A 0cb0f09ace81
release is a skill published in the GitHub repository lycorp-jp/sim-use (1,532 stars, last pushed 13d ago), licensed Apache-2.0. It adds 61 tokens to every session and 2,100 once invoked, about $0.0002 per session on Opus 5.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.
release compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| releaselycorp-jp/sim-use | Skill | 1.5k | 13d ago | Apache-2.0 | A | 61 | Claude Code, Codex |
| shipplugin87/ux-ui-agent-skills | Skill | 3.1k | 10d ago | MIT | A | 34 | Claude Code |
| swarm-migrateyonatangross/orchestkit | Skill | 299 | yesterday | MIT | A | 103 | Claude Code |
| release-managementyonatangross/orchestkit | Skill | 299 | yesterday | MIT | A | 58 | Claude Code |
| release-syncyonatangross/orchestkit | Skill | 299 | yesterday | MIT | A | 62 | Claude Code |
| daily-briefingCommunity-Access/accessibility-agents | Skill | 435 | 7d ago | MIT | A | 21 | Claude Code, Codex |
| release-managerCommunity-Access/accessibility-agents | Skill | 435 | 7d ago | MIT | A | 17 | Claude Code, Codex |