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.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/instructions/lycorp-jp/sim-use/agents-md)<a href="https://agentmods.dev/instructions/lycorp-jp/sim-use/agents-md"><img src="https://agentmods.dev/badge/instructions/lycorp-jp/sim-use/agents-md/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/instructions/lycorp-jp/sim-use/agents-md"><img src="https://agentmods.dev/badge/instructions/lycorp-jp/sim-use/agents-md.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.02896 | $0.02896 |
| Opus 5.5 | $0.01158 | $0.01158 |
| Sonnet 5.5 | $0.00579 | $0.00579 |
| Haiku 4.5 | $0.00290 | $0.00290 |
Grade A, and why
sim-use AGENTS.md 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Rules
Code quality
- No
Anytypes unless absolutely necessary; upgrade dependencies rather than downgrading code to work around type errors. - Follow Swift best practices and match the style of surrounding code.
- When adding or removing commands/options, update the README and
skills/sim-use/SKILL.md. If the Skill starts relying on behavior newer than its current compatibility floor, also bumpMINIMUM_SIM_USE_VERSIONinskills/sim-use/scripts/preflight.pyand extendPreflightScriptTests.
Changelog
CHANGELOG.md is a release guide for tool users, not an implementation log. Follow Keep a Changelog.
- Add changes under
## [Unreleased]. Released headings use## [x.y.z] - YYYY-MM-DD; do not edit released sections unless the user explicitly asks. - Start each populated version, including Unreleased, with a 1–3 sentence summary. Assume the reader reads only this summary: name the main benefits and any required migration.
- Use only non-empty subsections in this order:
### Added/### Changed/### Fixed/### Removed. Put the most important changes first within each subsection. - Write each bullet in plain English, usually 1–2 short sentences and at most about 50 words. State what users can do now or what problem is solved. Name commands or flags when useful, but explain their benefit or required action too.
- Combine related changes instead of listing every commit. Keep implementation details, investigation history and benchmark logs out of the changelog; use
docs/ai/for technical reasoning and the README for usage details. - Keep PR references and contributor thanks with the relevant change, including when merging or rewriting entries. Do not lose credit to save space. Describe each version as it shipped, without importing later behavior.
Design records (docs/ai/)
sim-use uses AI-docs-driven development. Before a substantial feature, a contract change (daemon or bridge wire, --json envelope, skill compatibility floor) or a non-trivial root-cause fix, create docs/ai/NNN-<slug>/000-plan.md (000-investigation.md for a root-cause hunt) with the write-ai-docs skill. Record each decision when you make it, and write 001-action.md after the work lands. Before you change code that an entry covers, read the entry. Index and layout: docs/ai/README.md.
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 · +7 lines · +212 tokens per session ee46dcb4c271
- 23d ago Changed · +3 lines · +145 tokens per session 639d4e73e0c6
- 29d ago Changed · +3 lines · +233 tokens per session 56730636b78b
- 1mo ago Changed · +26 lines · +323 tokens per session 02f146b3baf2
- 1mo ago Changed · +42 tokens per session c261ee4f1bc3
- 2mo ago First seen · 126 lines · 1,941 tokens per session scan A e66a0db2a3b2
sim-use AGENTS.md is an instructions file published in the GitHub repository lycorp-jp/sim-use (1,532 stars, last pushed 13d ago), licensed Apache-2.0. It adds 2,896 tokens to every session, about $0.0116 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.
sim-use AGENTS.md compared with instructions from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sim-use AGENTS.mdlycorp-jp/sim-use | Instructions file | 1.5k | 13d ago | Apache-2.0 | A | 2,896 | Codex, OpenCode |
| vscode buildNext.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 9,719 | GitHub Copilot |
| next.js AGENTS.mdvercel/next.js | Instructions file | 143k | today | MIT | A | 7,461 | Codex, OpenCode |
| langchain AGENTS.mdlangchain-ai/langchain | Instructions file | 149k | yesterday | MIT | A | 4,680 | Codex, OpenCode |
| vscode oss-third-party-notices.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 5,516 | GitHub Copilot |
| vscode copilot-instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 3,093 | GitHub Copilot |
| deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness | Instructions file | 274k | 2d ago | MIT | A | 4,313 | Codex, OpenCode |