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 commands/bentleypark/claude-code-mobile-spine/initgit clone --depth 1 https://github.com/bentleypark/claude-code-mobile-spineWrote 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/commands/bentleypark/claude-code-mobile-spine/init)<a href="https://agentmods.dev/commands/bentleypark/claude-code-mobile-spine/init"><img src="https://agentmods.dev/badge/commands/bentleypark/claude-code-mobile-spine/init.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.00013 | $0.00393 |
| Opus 5 | $0.00006 | $0.00197 |
| Sonnet 5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
init 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.
What it actually says
/mobile-spine:init
Run the mobile-spine:init skill bundled with this plugin: a 6-question interview that scaffolds a mobile-spine workspace. The scaffold writes workspace-owned data only — CLAUDE.md, SETUP.md, README.md, LICENSE, .gitignore, .claude/settings.json, .claude/mobile-spine.config.yaml (from the interview), .claude/commands/feat.md (thin stub → /mobile-spine:feat), _context/operations.md, and .gitkeep placeholders under _context/api/, _context/design/, _tasks/.
The four subagents (api-agent, pm-agent, android-agent, ios-agent) and the full /feat command logic are not scaffolded — they're plugin primitives served globally from plugins/mobile-spine/agents/ and plugins/mobile-spine/commands/. /plugin marketplace update claude-code-mobile-spine propagates updates to them automatically.
The skill body lives at ${CLAUDE_PLUGIN_ROOT}/skills/init/SKILL.md — read that file first and follow its instructions verbatim. The skill resolves the templates directory via ${CLAUDE_PLUGIN_ROOT}/skills/init/templates/, interviews the user, applies the (now-reduced v2.0) substitution scope to the doc templates, writes .claude/mobile-spine.config.yaml from the interview answers, and scaffolds to the chosen install location.
Important: do not deviate from the skill's substitution rules in §4-2, the config-write step in §4-3, or the sanity checks in §4-4 — they encode the placeholder discipline that keeps the scaffold consistent across users.
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 · 15 lines · 13 tokens per session scan A 72ea5357d35e
init is a command published in the GitHub repository bentleypark/claude-code-mobile-spine (1 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 393 once invoked, about $0.0001 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 commands, from other repositories
audit
Scan a codebase for existing observability instrumentation and identify gaps.
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
mobile-verify
Run automated verification loops with pass@k metrics for mobile testing. Executes tests multiple times to detect flakiness.
mobile-checkpoint
Save and restore mobile development checkpoints. Capture build variants, test states, and project state before risky operations.
platform-info
Detect project type (Android/iOS/KMP), list platforms, show platform info, and delegate to appropriate commands.
mobile-test
Unified mobile test command. Detects platform (Android/iOS/KMP) and delegates to appropriate test command.