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/profilegit 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/profile)<a href="https://agentmods.dev/commands/kasempiternal/axiom-v2/profile"><img src="https://agentmods.dev/badge/commands/kasempiternal/axiom-v2/profile.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.00019 | $0.00243 |
| Opus 5 | $0.00010 | $0.00121 |
| Sonnet 5 | $0.00004 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
profile 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
Profile Performance
Launches the performance-profiler agent to record and analyze performance traces using xctrace CLI.
What It Does
The agent will:
- Detect available simulators and running apps
- Help you select what to profile
- Record a trace with the appropriate instrument (CPU Profiler, Allocations, Leaks, SwiftUI)
- Export and analyze the data programmatically
- Report findings with severity and recommendations
Supported Instruments
- CPU Profiler -- Find hot functions and CPU bottlenecks
- Allocations -- Track memory usage and growth
- Leaks -- Detect memory leaks
- SwiftUI -- Analyze view body updates
- Swift Tasks/Actors -- Concurrency analysis
Prefer Natural Language?
- "Profile my app's CPU usage"
- "Run Time Profiler on my app"
- "Check for memory leaks"
- "Profile my app's launch time"
- "Run a headless performance trace"
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 · 35 lines · 19 tokens per session scan A ea360fb4ec04
profile is a command published in the GitHub repository Kasempiternal/axiom-v2 (4 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 243 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
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
OPSX: Sync
Sync delta specs from a change to main specs.
ml-impl
Full implementation loop - plan, write, and review code (Meta-Loop Steps 3.1-3.4).