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.
git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observabilityWrote 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/nexus-labs-automation/mobile-observability/audit)<a href="https://agentmods.dev/commands/nexus-labs-automation/mobile-observability/audit"><img src="https://agentmods.dev/badge/commands/nexus-labs-automation/mobile-observability/audit/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.
<a href="https://agentmods.dev/commands/nexus-labs-automation/mobile-observability/audit"><img src="https://agentmods.dev/badge/commands/nexus-labs-automation/mobile-observability/audit.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01253 |
| Opus 5 | $0.00000 | $0.00626 |
| Sonnet 5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00125 |
Grade A, and why
audit 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 9d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Command
Scan a codebase for existing observability instrumentation and identify gaps.
Usage
/audit [path]
Arguments:
path: Optional. Directory to scan (defaults to current directory)- Non-existent path: Error with "Path not found: [path]"
- Non-directory: Error with "Path must be a directory: [path]"
Examples:
/audit
/audit ./src
/audit ~/projects/my-app
Workflow
Step 1: Launch Codebase Analyzer
Invoke the codebase-analyzer agent to:
- Detect platform (iOS/Android/React Native)
- Identify architecture patterns
- Find existing telemetry SDKs
- Map instrumentation coverage
Step 2: Load Reference Context
Read:
references/instrumentation-patterns.md- Instrumentation checklistreferences/platforms/*.md- Vendor-specific patterns
Step 3: Evaluate Coverage
Check each instrumentation area against the codebase:
| Area | What to Find | Priority |
|---|---|---|
| SDK Init | SDK setup in AppDelegate/Application | P0 |
| Crash Reporting | Error capture, crash handlers | P0 |
| User Context | setUser, user ID setting |
P0 |
| Symbolication | dSYM upload, ProGuard config | P0 |
| App Start | Launch timing, startup spans | P1 |
| Screen Load | TTI tracking, screen spans | P1 |
| Network | Request interceptors, API tracing | P1 |
| Breadcrumbs | Navigation/action logging | P1 |
| Database | Query tracing | P2 |
| Custom Spans | Business flow instrumentation | P2 |
Step 4: Identify Anti-Patterns
Flag issues like:
- PII in breadcrumbs/logs
- Synchronous telemetry on main thread
- Missing symbolication config
- Over-instrumentation (battery impact)
- Inconsistent span naming
Step 5: Generate Report
Output format:
## Telemetry Audit Report
### Platform
- **Type:** [iOS/Android/React Native]
- **Language:** [Swift/Kotlin/TypeScript]
### Existing SDKs
| SDK | Version | Location | Status |
|-----|---------|----------|--------|
| Sentry | 8.0.0 | Podfile:23 | Active |
| Firebase | 10.0.0 | Podfile:25 | Crashlytics only |
### Coverage Assessment
| Area | Status | Details |
|------|--------|---------|
| Crash Reporting | ✅ Covered | Sentry SDK initialized in AppDelegate |
| Error Tracking | ⚠️ Partial | Only in network layer |
| App Start | ❌ Missing | No launch timing |
| Screen Load | ⚠️ Partial | 3/12 screens tracked |
| Network | ✅ Covered | URLSession instrumented |
| Breadcrumbs | ❌ Missing | No breadcrumb logging |
| User Context | ✅ Covered | User ID set on login |
| Symbolication | ⚠️ Partial | dSYM upload configured, but not verified |
### Coverage Score: 62%
Foundation: ████████░░ 80% Performance: ████░░░░░░ 40% Context: ██░░░░░░░░ 20% Advanced: ░░░░░░░░░░ 0%
### Gaps Identified
| Gap | Priority | Impact | Effort |
|-----|----------|--------|--------|
| No app start tracking | P1 | Can't measure launch perf | Low |
| No screen load TTI | P1 | Can't identify slow screens | Medium |
| No breadcrumbs | P1 | Poor crash debugging | Low |
| Missing database spans | P2 | Can't trace slow queries | Medium |
### Anti-Patterns Found
1. **[Issue]** - [Location] - [Recommendation]
### Recommendations
#### Quick Wins (This Week)
1. [Low effort, high impact items]
#### Medium Term (This Month)
1. [Moderate effort items]
#### Nice to Have
1. [Lower priority items]
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.
- 9d ago First seen · 190 lines · 0 tokens per session scan A 8e5bd1e78a76
audit is a command published in the GitHub repository nexus-labs-automation/mobile-observability (116 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,253 tokens. 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 commands, from other repositories
feature-learn
View and manage patterns learned from feature builds. Shows extracted instincts, confidence scores, and feature completeness history.
feature-build
Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.
feature-plan
Plan a mobile feature with architecture decisions, file breakdown, dependency analysis, and test strategy. Produces a structured plan document reviewed by an architecture agent.
feature-implement
Implement a planned mobile feature using parallel specialized agents for network, data, architecture, UI, and wiring layers. Requires an approved feature plan.
feature-status
Show the current status of a feature build - which phase is active, what has completed, what remains, and any blockers.
feature-test
Create all tests for an implemented feature - unit tests (ViewModel, UseCase, Repository), Compose UI tests, and E2E user flow tests.