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/okminlee/everything-claude-code-ios/ios-coveragegit clone --depth 1 https://github.com/OkminLee/everything-claude-code-iosWhat 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.00030 | $0.02141 |
| Opus 5 | $0.00015 | $0.01071 |
| Sonnet 5 | $0.00006 | $0.00428 |
| Haiku 4.5 | $0.00003 | $0.00214 |
Grade A, and why
ios-coverage scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
bash <(curl -s https://codecov.io/bash) -f coverage.lcov How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Test Coverage
Analyze test coverage and generate missing tests for iOS projects.
What This Command Does
- Run Tests with Coverage - Execute tests with code coverage enabled
- Analyze Coverage Report - Parse xcresult bundle with xccov
- Identify Gaps - Find files below 80% threshold
- Generate Missing Tests - Create unit/integration tests
- Verify and Report - Show before/after metrics
Process
-
Run tests with coverage:
xcodebuild test \ -scheme MyApp \ -destination 'platform=iOS Simulator,name=iPhone 16' \ -enableCodeCoverage YES \ -resultBundlePath TestResults.xcresult -
Analyze coverage report:
xcrun xccov view --report TestResults.xcresult -
Identify files below 80% coverage threshold
-
For each under-covered file:
- Analyze untested code paths
- Generate unit tests for functions
- Generate integration tests for repositories
- Identify edge cases to cover
-
Verify new tests pass
-
Show before/after coverage metrics
-
Ensure project reaches 80%+ overall coverage
Running Coverage Analysis
Xcode Project
# Run tests with coverage
xcodebuild test \
-scheme MyApp \
-destination 'platform=iOS Simulator,name=iPhone 16' \
-enableCodeCoverage YES \
-resultBundlePath TestResults.xcresult
# View summary report
xcrun xccov view --report TestResults.xcresult
# View JSON report (for parsing)
xcrun xccov view --report --json TestResults.xcresult > coverage.json
# View specific file coverage
xcrun xccov view --archive --file Sources/HomeViewModel.swift TestResults.xcresult
Swift Package
# Run with coverage
swift test --enable-code-coverage
# Find coverage data
COVERAGE_PATH=$(swift test --show-codecov-path)
# Convert to report
xcrun llvm-cov report \
.build/debug/MyPackagePackageTests.xctest/Contents/MacOS/MyPackagePackageTests \
-instr-profile=$COVERAGE_PATH
Coverage Report Format
╔══════════════════════════════════════════════════════════════╗
║ Coverage Report ║
╠══════════════════════════════════════════════════════════════╣
║ Overall Coverage: 72.4% (Target: 80%) ║
║ Status: ❌ BELOW THRESHOLD ║
╚══════════════════════════════════════════════════════════════╝
## Coverage by Target
| Target | Coverage | Status |
|--------|----------|--------|
| MyApp | 68.2% | ❌ |
| MyAppTests | 100% | ✅ |
## Files Below Threshold (<80%)
| File | Coverage | Lines Missed | Priority |
|------|----------|--------------|----------|
| HomeViewModel.swift | 45.2% | 28/51 | 🔴 HIGH |
| NetworkClient.swift | 62.1% | 19/50 | 🟡 MEDIUM |
| UserService.swift | 78.3% | 5/23 | 🟢 LOW |
## Untested Code Paths
### HomeViewModel.swift (45.2%)
**Untested Functions:**
1. `fetchItems()` - Line 23-45
- Error handling path not tested
- Empty result case not tested
2. `deleteItem(id:)` - Line 67-89
- Entire function untested
3. `refreshData()` - Line 102-115
- Cancellation path not tested
**Recommended Tests:**
```swift
@Test func fetchItems_onError_showsAlert() async {
// Test error handling path
}
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 · 334 lines · 30 tokens per session scan A fa7daf142db0
ios-coverage is a command published in the GitHub repository OkminLee/everything-claude-code-ios (58 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 2,141 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
android
Command "android" from zhagqn/agentwork, covering /android [subcommand] [args] and 执行前必读.
compose-test
Run Compose UI tests with Espresso. Verify critical user flows.
troubleshoot
Diagnose and resolve iOS issues in code, builds, runtime, and system behavior.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
build-verify
Run the full build / test / analyze / format verification pass for this Flutter app.
ios-privacy
Prepare privacy labels, permissions, policy links, and data-use truth for iOS release.