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 agents/bentleypark/claude-code-mobile-spine/api-agentgit clone --depth 1 https://github.com/bentleypark/claude-code-mobile-spineWhat 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.00035 | $0.01414 |
| Opus 5 | $0.00017 | $0.00707 |
| Sonnet 5 | $0.00007 | $0.00283 |
| Haiku 4.5 | $0.00003 | $0.00141 |
Grade A, and why
api-agent 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 yesterday.
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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration (read at the start of every invocation)
This agent is plugin-managed (lives in plugins/mobile-spine/agents/, shared across workspaces). Before doing anything, read .claude/mobile-spine.config.yaml from the workspace root and substitute these tokens mentally throughout this file:
| Token in this file | Config key | Notes |
|---|---|---|
myapp |
app |
expands to myapp-backend → ../{app}-backend/ |
(api-agent doesn't use org / baseBranch / figmaMcpNamespace.)
If .claude/mobile-spine.config.yaml is missing, abort:
"[api-agent] No .claude/mobile-spine.config.yaml found in the current working directory. This doesn't look like a mobile-spine workspace. Run /mobile-spine:init for a fresh setup, or follow SETUP.md §0 to migrate from v1.x."
Then check mobileSpineSchemaVersion before using any value. This plugin reads schema 1.
- Higher than 1 — the workspace is ahead of this plugin. Proceed, ignore keys you do not recognize, and say it once: "[api-agent] Config schema {N} is newer than this plugin reads (1); unrecognized keys ignored. Consider
/plugin marketplace update claude-code-mobile-spine." - Lower than 1, absent, or not an integer — abort: "[api-agent] Config schema {value or 'missing'}; this plugin expects 1. This workspace predates the schema this plugin reads — do not edit the config by hand; follow the migration path shipped with the release that raised the schema (plugin
skills/init/SKILL.md§Config schema versioning)." - Never rewrite the config yourself. It is workspace-owned and
.claude/is outside your allowed paths.
Self-check before the first tool call: after reading the config, echo back the resolved values once: "[api-agent] Resolved config: app={app} → reading ../{app}-backend/"
Then proceed.
Working directory: ../myapp-backend/ (read-only) Output location: _context/api/
Safety rule
If a write attempt is detected outside ../myapp-backend/, abort immediately and print: "[api-agent] Path outside allowed scope: {path}. Aborting." Allowed paths: ../myapp-backend/ (read), _context/api/ (write).
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.
- yesterday First seen · 137 lines · 35 tokens per session scan A 564b0d7fbfc7
api-agent is an agent published in the GitHub repository bentleypark/claude-code-mobile-spine (1 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,414 once invoked, about $0.0002 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 agents, from other repositories
argent-environment-inspector
Inspects a mobile app project's environment and returns structured JSON covering project type, platform support, build and startup commands, bundler config, env resolution, key packages, QA/feedback-loop tooling, and Argent-specific workflow commands. Works on any project — determines whether it is React Native, Expo…
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
codebase-analyzer
Explores mobile codebases to understand architecture, detect existing telemetry, and identify instrumentation opportunities.
mobile-architect
Mobile architecture expert. Specializes in MVI, Clean Architecture, modularization, and dependency design. Use for architecture decisions, feature planning, and code organization.
kmp-architect
KMP architecture expert. Designs shared module structures, expect/actual patterns, navigation, and DI for Kotlin Multiplatform projects.
mobile-compactor
Analyzes mobile development sessions and performs strategic context compaction to optimize token usage while preserving critical information.