sim-use AGENTS.md

A set of development instructions for lycorp-jp/sim-use, a Swift project for working with iOS simulators. It covers code quality, changelog updates, setup, building, and testing.

In plain words
What is it for?
Use it when developing sim-use, adding or removing commands, updating documentation, switching Xcode versions, building the project, or testing against a booted simulator.
Why use it?
It gives contributors consistent rules for changing the project and running its required build and test commands.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/lycorp-jp/sim-use/agents-md
Clone the repo
git clone --depth 1 https://github.com/lycorp-jp/sim-use

Made for: Codex, OpenCode.

Per session 1,941 This file is loaded in full into every session.
When invoked 1,941 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01941 $0.01941
Opus 5 $0.00971 $0.00971
Sonnet 5 $0.00388 $0.00388
Haiku 4.5 $0.00194 $0.00194

Measured 2d ago against content hash e66a0db2a3b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

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.

AGENTS.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Development Rules

Code quality

  • No Any types 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.

Changelog

CHANGELOG.md follows Keep a Changelog. Add entries under ## [Unreleased] as you land changes. Subsection order: ### Added / ### Changed / ### Fixed / ### Removed. Never modify already-released version sections.

Build and test

First-time setup

brew install xcodegen    # idb generates its Xcode project with XcodeGen
./scripts/build.sh dev   # clone idb, build XCFrameworks
make build               # build sim-use

The FB* XCFrameworks are static archives built without library evolution — build_products/ is locked to the toolchain that produced it. Re-run ./scripts/build.sh dev after switching Xcode versions.

Daily workflow

make build                                           # incremental build
.build/debug/sim-use describe-ui --device $UDID      # test against a booted simulator

Running tests

make test                        # unit tests (no simulator needed)
swift test --filter TapTests     # run a single test suite

make test runs swift test --enable-code-coverage — unit tests that exercise parsing, outline rendering, daemon protocol, and cross-platform dispatch without a live simulator.

When xcsift is installed (brew install xcsift — optional, never required), make build / make test condense swift output into a TOON summary plus a coverage report. SIM_USE_XCSIFT=0 make test forces plain swift output.

End-to-end tests (live device)

make e2e            # BOTH iOS + Android in sequence (needs a booted sim AND an emulator)
make e2e-ios        # iOS only — booted simulator + Playground fixture
make e2e-android    # Android only — reachable device/emulator + Playground fixture
make e2e-matrix     # iOS across Xcode 26/27 × Device Hub closed/open legs (~35 min default)
make eval           # agent evals (real `claude -p` cost; prompts before running)

Read the full file on GitHub · 126 lines

Changes

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.

  1. 2d ago First seen · 126 lines · 1,941 tokens per session scan A e66a0db2a3b2

Subscribe to this mod's changes

sim-use AGENTS.md is an instructions file published in the GitHub repository lycorp-jp/sim-use (1,297 stars, last pushed 5d ago), licensed Apache-2.0. It adds 1,941 tokens to every session, about $0.0097 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-30.