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/kasempiternal/axiom-v2/statusgit clone --depth 1 https://github.com/Kasempiternal/axiom-v2Wrote 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/kasempiternal/axiom-v2/status)<a href="https://agentmods.dev/commands/kasempiternal/axiom-v2/status"><img src="https://agentmods.dev/badge/commands/kasempiternal/axiom-v2/status.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.1 | $0.00010 | $0.00459 |
| Opus 5 | $0.00005 | $0.00230 |
| Sonnet 5 | $0.00002 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
status 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 5d 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
You are a project health analyzer. Provide a quick dashboard of the iOS project state.
Gather Information
Run these checks and format as a dashboard:
Environment Health
# Zombie processes
pgrep -f xcodebuild | wc -l
# Derived Data size
du -sh ~/Library/Developer/Xcode/DerivedData 2>/dev/null
# Simulator status (JSON for reliable parsing)
xcrun simctl list devices -j | jq '.devices | to_entries[] | .value[] | select(.state == "Booted") | {name, udid}'
# Tool availability
echo "jq: $(command -v jq &>/dev/null && echo 'installed' || echo 'NOT INSTALLED')"
echo "axe: $(command -v axe &>/dev/null && echo 'installed (UI automation available)' || echo 'not installed (optional)')"
Project Analysis
# Count SwiftUI views
find . -name "*.swift" -exec grep -l "struct.*View.*body" {} \; | wc -l
# Check for potential issues
grep -r "Timer\|NotificationCenter\.default\.addObserver" --include="*.swift" | wc -l
# iOS deployment target
grep -r "IPHONEOS_DEPLOYMENT_TARGET" *.xcodeproj/project.pbxproj 2>/dev/null | head -1
Format as Dashboard
Axiom Project Status
=====================
Environment
Xcodebuild processes: [count] [warning if > 3]
Derived Data: [size] [warning if > 10GB]
Simulators running: [count]
jq: [installed/NOT INSTALLED]
axe: [installed/not installed (optional)]
Project Analysis
SwiftUI views: [count]
Potential memory patterns: [count] [warning if > 0]
Deployment target: iOS [version]
Suggested Actions
[Based on findings, suggest 2-3 most relevant audits]
[If jq not installed: "Install jq: brew install jq"]
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.
- 5d ago First seen · 61 lines · 10 tokens per session scan A 41db7a57bb4d
status is a command published in the GitHub repository Kasempiternal/axiom-v2 (4 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 459 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
mobile-verify
Run automated verification loops with pass@k metrics for mobile testing. Executes tests multiple times to detect flakiness.
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-status
Show the current status of a feature build - which phase is active, what has completed, what remains, and any blockers.
platform-info
Detect project type (Android/iOS/KMP), list platforms, show platform info, and delegate to appropriate commands.
ios-test
Run iOS tests with xcodebuild, show coverage. Invokes ios-testing patterns.