instrumentation-planning

instrumentation-planning is a skill for Claude Code from nexus-labs-automation/mobile-observability. It costs 31 tokens per session (520 once invoked), scanned A, original, MIT.

A guide for deciding what data to collect from a mobile app, such as crashes, loading times, user actions, and feature use.

In plain words
What is it for?
Use it when starting app monitoring or deciding which crashes, errors, performance details, and user outcomes to track.
Why use it?
It helps teams choose useful measurements without collecting everything, which can create noise and drain battery.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the mobile-observability plugin — 8 skills, 2 commands, 2 agents shipped together

Good fit Use it when starting app monitoring or deciding which crashes, errors, performance details, and user outcomes to track.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nexus-labs-automation/mobile-observability/instrumentation-planning
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.

Any agent
npx skills add nexus-labs-automation/mobile-observability --skill instrumentation-planning
Clone the repo
git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability

Made for: Claude Code.

Or install mobile-observability, the plugin that ships this one along with the rest of its 8 skills, 2 commands, 2 agents.

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

agentmods badge for instrumentation-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/nexus-labs-automation/mobile-observability/instrumentation-planning/github.svg)](https://agentmods.dev/skills/nexus-labs-automation/mobile-observability/instrumentation-planning)
Your own site
<a href="https://agentmods.dev/skills/nexus-labs-automation/mobile-observability/instrumentation-planning"><img src="https://agentmods.dev/badge/skills/nexus-labs-automation/mobile-observability/instrumentation-planning/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for instrumentation-planning

Your own site · 80×15
<a href="https://agentmods.dev/skills/nexus-labs-automation/mobile-observability/instrumentation-planning"><img src="https://agentmods.dev/badge/skills/nexus-labs-automation/mobile-observability/instrumentation-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 520 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00031 $0.00520
Opus 5 $0.00015 $0.00260
Sonnet 5 $0.00006 $0.00104
Haiku 4.5 $0.00003 $0.00052

Measured 12d ago against content hash 56c38dce3e80, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

instrumentation-planning 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 12d 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.

skills/instrumentation-planning/SKILL.md · 76 lines

What it actually says

Instrumentation Planning

Strategic guidance for what to measure using Jobs-to-be-Done framework.

Core Question

For each user job, ask:

  • Did it complete? → completion rate
  • How long? → duration (p50, p95, p99)
  • What failed? → error type, context
  • Did they give up? → drop-off rate

Priority Tiers

Tier Focus Examples
1 Crashes & errors Crash reporting, error boundaries
2 User context User ID, session ID, device info
3 Performance App start, screen load, network
4 Breadcrumbs Navigation, user actions
5 Business metrics Funnels, feature usage

Implementation Order

Day 1:  Crash reporting + User context
Week 1: Breadcrumbs + Release tracking
Week 2: Performance spans
Month 1: Business metrics

Future-Proofing

Use OTel-compatible span/attribute names now (zero cost, easier migration later):

  • http.request.method not method
  • ui.screen.load not screenLoad
  • app.start.cold not coldStart

See references/otel-mobile.md for full naming conventions.

Anti-Patterns

  • Measure everything (noise, battery drain)
  • Skip symbolication (unreadable crashes)
  • Block main thread for telemetry
  • Log PII in breadcrumbs

Implementation

See references/instrumentation-patterns.md for:

  • Detailed 5-tier checklist
  • Span naming conventions
  • Sampling strategies
  • Testing checklist

See references/jtbd.md for full Jobs-to-be-Done framework.

  • See skills/user-journey-tracking for implementing JTBD instrumentation
  • See skills/crash-instrumentation for Tier 1 (crashes)
  • See skills/symbolication-setup for Tier 1 (readable stack traces)
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. 12d ago First seen · 76 lines · 31 tokens per session scan A 56c38dce3e80

Subscribe to this mod's changes

instrumentation-planning is a skill published in the GitHub repository nexus-labs-automation/mobile-observability (116 stars, last pushed 19d ago), licensed MIT. It adds 31 tokens to every session and 520 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-30.

Related

Other skills, from other repositories

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…

software-mansion/argent · 78 tokens

argent-metro-debugger

Debug a JS runtime via CDP using argent debugger tools. Primary path is React Native via Metro (iOS / Android / Vega); a subset of the tools (debugger-connect, debugger-status, debugger-evaluate, debugger-log-registry) also drive a Chromium (CDP) app's renderer (an Electron app, or any Chromium browser exposing CDP)…

software-mansion/argent · 104 tokens

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…

software-mansion/argent · 140 tokens

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.

software-mansion/argent · 71 tokens

truesheet-usage

Consumer-side guide for integrating @lodev09/react-native-true-sheet into a React Native app. Use this skill whenever the user wants to add, configure, control, or debug a bottom sheet using TrueSheet — including ref-based sheets, named global sheets, web support with TrueSheetProvider/useTrueSheet, React Navigation…

lodev09/react-native-true-sheet · 169 tokens

mobile-automation

Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.

mobile-next/mobile-mcp · 58 tokens