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/lycorp-jp/sim-use/releasenpx skills add lycorp-jp/sim-use --skill releasegit clone --depth 1 https://github.com/lycorp-jp/sim-useWhat 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.00061 | $0.01832 |
| Opus 5 | $0.00030 | $0.00916 |
| Sonnet 5 | $0.00012 | $0.00366 |
| Haiku 4.5 | $0.00006 | $0.00183 |
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 3d 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 — 153 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/xxxx-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.
- 3d 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,297 stars, last pushed 6d ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,832 once invoked, about $0.0003 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.
Other skills, from other repositories
prepare-release
End-to-end release automation — reads commits since last tag, infers semver bump, drafts changelog, creates release PR, merges it, waits for CI green, tags, and monitors the Docker build to completion. Use when the user says: prepare release, cut a release, bump version, create release PR, ship a new version, tag a…
release
Release a new version of BranchBox. Use when the user says "release", "new version", "cut a release", "publish release", or "tag version". Handles version bumping, changelog updates, quality checks, and GitHub release workflow.
git-conventional-commits
Prepare scoped conventional commits, tags, and release messages.
release
Release a new version of iosef. Use when the user asks to release, publish, tag a version, or push to PyPI. Handles version bumping, building, tagging, and pushing. Do NOT use for regular development pushes to main (use jj-just-push-main for that).
open-gui-remote-control
Control an Android phone through OpenGUI from an AI coding agent such as Claude Code, Codex, or OpenCode. Use when an agent should list online devices, run a natural-language mobile task, check execution status, pause, resume, or cancel through the local OpenGUI backend and CLI.
release-notes
Generate SEO-optimized GitHub release notes for kwin-mcp.