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/Xopoko/build-swift-appsWrote 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/xopoko/build-swift-apps/macos-test-diagnose)<a href="https://agentmods.dev/commands/xopoko/build-swift-apps/macos-test-diagnose"><img src="https://agentmods.dev/badge/commands/xopoko/build-swift-apps/macos-test-diagnose/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/xopoko/build-swift-apps/macos-test-diagnose"><img src="https://agentmods.dev/badge/commands/xopoko/build-swift-apps/macos-test-diagnose.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.00198 |
| Opus 5 | $0.00000 | $0.00099 |
| Sonnet 5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
macos-test-diagnose 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.
This is a copy
95% identical to test-macos-app — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/macos-test-diagnose
Run the smallest meaningful macOS test scope first and explain failures by category.
Arguments
scheme: Xcode scheme name (optional)target: test target or product name (optional)filter: test filter expression (optional)configuration:DebugorRelease(optional, default:Debug)
Workflow
- Detect whether the repo uses
xcodebuild testorswift test. - Prefer focused test execution when a target or filter is provided.
- Classify failures as compile, assertion, crash, env/setup, or flake.
- Summarize the top blocker and the narrowest sensible next step.
Guardrails
- Avoid rerunning the full suite if a focused rerun is possible.
- Distinguish build failures from actual failing tests.
- Note when host app setup or simulator-only test assumptions leak into a macOS run.
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 · 24 lines · 0 tokens per session scan A 84644a27ed4d
macos-test-diagnose is a command published in the GitHub repository Xopoko/build-swift-apps (45 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 198 tokens. A static security scan graded it A with 0 findings. It is 95% identical to test-macos-app, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
add-tests
Add tests for recently changed files or specified code.
meta-theory-verify
Run the appropriate MetaKim verification path.
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
ui-aqa-flow-code-analysis
Phase 3 Code Analysis of ui-aqa-flow.