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/forgeyclap/claude-forge/forge-mobilenpx skills add ForgeyClap/claude-forge --skill forge-mobilegit clone --depth 1 https://github.com/ForgeyClap/claude-forgeWrote 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/forgeyclap/claude-forge/forge-mobile)<a href="https://agentmods.dev/skills/forgeyclap/claude-forge/forge-mobile"><img src="https://agentmods.dev/badge/skills/forgeyclap/claude-forge/forge-mobile.svg" alt="Measured on agentmods" 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 | $0.00050 | $0.01311 |
| Opus 5 | $0.00025 | $0.00656 |
| Sonnet 5 | $0.00010 | $0.00262 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
forge-mobile 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 4d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge playbook — Mobile app (React Native / Expo / Flutter)
The mobile-dev specialist leads the native work under build-boss. Native UX/touch/layout defers to ui-boss; any backend/API the app calls defers to forge-integration; if it handles money defer to forge-payments. The core honesty rule for mobile: a Metro/dev bundler running is not a shipped app — the release binary must actually build and launch on a real device or emulator, and you must say so with evidence.
Hard rules (non-negotiable)
- A native build that actually installs. The app compiles to the real artifact (Android
.apk/.aab, iOS.ipa, or an Expo dev/prod build) and installs + launches on a device or emulator/simulator — verified, not assumed. "It runs in Expo Go / Metro" is not proof a standalone build works. - No secrets in the client bundle. A mobile bundle is trivially extractable (decompile the APK, read the JS bundle). Real secrets (API signing keys, private tokens) stay server-side behind an API; only genuinely public keys ship. Nothing sensitive committed or baked into the binary.
- Secure token storage. Auth tokens / credentials live in the OS secure store —
expo-secure-store,react-native-keychain(iOS Keychain / Android Keystore), or Flutterflutter_secure_storage— neverAsyncStorage/SharedPreferences/ plain files. - Least-privilege permissions with rationale. Request only permissions the app actually uses; iOS requires a real usage-description string per permission (
NSCameraUsageDescription, etc.) or App Store rejection; Android manifest kept minimal. - Offline-where-promised actually works. If offline use is promised, cached reads, queued writes, and a clear "no connection" state exist — not network calls that silently fail.
- No test/demo/mock data, no debug menus, no
__DEV__-only shortcuts in the release build. Release signing configured (Android release keystore, iOS distribution), version/build numbers set, app icon + splash present.
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.
- 4d ago First seen · 39 lines · 50 tokens per session scan A 0571dd684339
forge-mobile is a skill published in the GitHub repository ForgeyClap/claude-forge (2 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 1,311 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-31.
Other skills, from other repositories
canvas
Display, present, and render HTML content on connected Otto nodes (Mac app, iOS, Android). Show on device, preview on mobile, push to screen, or navigate to a URL on any connected node. Use for games, visualizations, dashboards, interactive demos, and live-reloading development previews. Supports presenting, hiding…
argent-device-interact
Interact with an iOS simulator, Android emulator, or Chromium (CDP) app using argent MCP tools. Use when tapping UI elements, performing gestures, scrolling/swiping, typing text, pressing hardware buttons, launching apps, opening URLs, taking screenshots, waiting for an element to appear or disappear, or checking…
argent-settings-permissions
Grant, deny, or reset an app's runtime permissions (camera, microphone, photos, contacts, notifications, calendar, location, location-always, media-library, motion, reminders) on an iOS simulator or Android device using the argent settings-permissions tool - without navigating the system Settings UI. Use when the…
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
argent-react-native-optimization
Optimizes a React Native app by profiling first to find real bottlenecks, then sweeping for mechanical issues. Entry-point for all performance work. Use when the app feels slow, user asks to optimize, fix re-renders, reduce jank, or improve startup. Delegates to argent-react-native-profiler for measurement.
gamified-app
三屏: 封面 / 今日任务带 XP / 任务详情, 暗色舞台.