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 agents/dekaprayoga/aurixagent/swift-build-resolvergit clone --depth 1 https://github.com/DekaPrayoga/AurixAgentWrote 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/dekaprayoga/aurixagent/swift-build-resolver)<a href="https://agentmods.dev/agents/dekaprayoga/aurixagent/swift-build-resolver"><img src="https://agentmods.dev/badge/agents/dekaprayoga/aurixagent/swift-build-resolver.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.00048 | $0.01702 |
| Opus 5 | $0.00024 | $0.00851 |
| Sonnet 5 | $0.00010 | $0.00340 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
swift-build-resolver 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 171 lines · 48 tokens per session scan A 3dc61451e2d4
swift-build-resolver is an agent published in the GitHub repository DekaPrayoga/AurixAgent (63 stars, last pushed 1mo ago), with no licence file. It adds 48 tokens to every session and 1,702 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
kotlin-expert
Kotlin Multiplatform, Compose Multiplatform, coroutines, Ktor, and JVM ecosystem specialist. Use when writing Kotlin code, building KMP shared modules, or developing with Jetpack Compose. Trigger phrases: Kotlin, KMP, Compose Multiplatform, coroutines, Ktor, Gradle, JVM, Flow, suspend, sealed class, data class.
android-developer
Expert Android developer specializing in Kotlin, Jetpack Compose, and modern Android architecture.
ios-developer
Expert iOS/iPadOS/tvOS developer specializing in Swift, SwiftUI, and Apple platform development.
macos-developer
Expert macOS native developer for AppKit, Catalyst, and macOS-specific features.
go-expert
Go programming language strategist. Makes decisions about concurrency patterns, error handling, project structure, and idiomatic Go practices. Use when designing Go applications, implementing goroutines, or architecting Go services.
python-expert
Strategic guidance for Python project architecture, package management with UV, code organization, and best practices. Use when designing Python projects, choosing packaging tools, or making architectural decisions for Python applications.