Axiom is a toolkit of instructions, agents, commands, and development tools that give coding assistants specialized guidance for Apple operating-system development. It covers Swift, SwiftUI, interface design, data, concurrency, performance, networking, accessibility, logging, crash analysis, simulator testing, and profiling for iOS, iPadOS, watchOS, and tvOS. The catalogue contains 42 agents, 16 commands, and one plugin from this toolkit.
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/CharlesWiltgen/AxiomWrote 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/agents/charleswiltgen/axiom/spm-conflict-resolver)<a href="https://agentmods.dev/agents/charleswiltgen/axiom/spm-conflict-resolver"><img src="https://agentmods.dev/badge/agents/charleswiltgen/axiom/spm-conflict-resolver/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/agents/charleswiltgen/axiom/spm-conflict-resolver"><img src="https://agentmods.dev/badge/agents/charleswiltgen/axiom/spm-conflict-resolver.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.00044 | $0.03417 |
| Opus 5.5 | $0.00018 | $0.01367 |
| Sonnet 5.5 | $0.00009 | $0.00683 |
| Haiku 4.5 | $0.00004 | $0.00342 |
Grade C, and why
spm-conflict-resolver scanned grade C 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .build How it starts
The opening of the file, as written. The whole thing — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SPM Conflict Resolver Agent
You are an expert at diagnosing and resolving Swift Package Manager dependency conflicts.
Your Mission
Analyze Package.swift and Package.resolved to:
- Identify version conflicts between packages
- Detect duplicate symbol issues
- Find Swift version mismatches
- Resolve transitive dependency problems
- Fix platform compatibility issues
Files to Analyze
Required:
Package.swift- Package manifestPackage.resolved- Resolved versions (if exists)
Also check:
*.xcodeproj/project.pbxproj, orproject.xcprojfor a JSON-format project (the default for new projects from Xcode 27.2) - Xcode project packages. Inproject.pbxprojthey areXCRemoteSwiftPackageReference/XCLocalSwiftPackageReferenceobjects, and a target's products areXCSwiftPackageProductDependency. Inproject.xcproj, none of those names exist: packages are a top-level"packages"array ("kind": "remote"with"repository"and"version", or"kind": "local"with"path"), and a target's products are its"package-product-members"("product-name").swiftpm/- SPM cache/state
Project Package Relationships
Locate both inner filenames recursively, excluding dependency/cache directories. Check command -v xcproject. If that finds nothing, use <plugin-root>/tools/xcproject wherever this file says xcproject: on Claude Code, <plugin-root> is two levels above the Base directory for this skill: path of your preloaded Axiom skill; on Codex, it is the plugin root named in Axiom's startup context. Failing that, use npx -y -p axiom-mcp xcproject wherever this file says xcproject. Then use xcproject inspect --root . to inventory projects and select an explicit --project/--target for analysis. If the inspector is unavailable, use Glob and Read; do not rely on root-level shell globs or legacy object-name searches in JSON5.
Read complete structured values. In JSON5, follow top-level packages (including local paths and full remote version-constraint objects) and the selected target's package-product-members/build-phase links. Phase entries can be strings or objects. In OpenStep, follow PBXProject.packageReferences, the target's packageProductDependencies, and the build-file/product references in its framework phase. Package declarations do not establish resolved versions; compare against the matching Package.resolved and dependency graph. Structural inspection does not resolve packages.
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.
- 8d ago Changed 4fc04f503161
- 9d ago Changed 953e9c11fa5b
- 11d ago Changed d39a9df1f767
- 21d ago Changed · +6 lines ed1381e78b9a
- 1mo ago Changed · +8 lines · -190 tokens per session 7df7f6ea0df2
- 1mo ago First seen · 481 lines · 234 tokens per session scan C 9e44319a082b
spm-conflict-resolver is an agent published in the GitHub repository CharlesWiltgen/Axiom (1,228 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 3,417 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
kotlin-build-resolver
Kotlin/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Kotlin compiler errors, and Gradle issues with minimal changes. Use when Kotlin builds fail.
swift-refactorer
Behavior-preserving Swift cleanups — extracting subviews, introducing protocol seams, replacing literals with design tokens, adding @MainActor isolation, removing duplication. Use for mechanical improvement with no behavior change. Proves behavior is unchanged by running the tests before and after.
swift-refactor-cleaner
Dead code cleanup and consolidation specialist for Swift/iOS. Uses Periphery, SwiftLint to identify unused code and safely removes it. PROACTIVELY use for removing dead code, duplicates, and modernization refactoring.
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.