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/Nagarjuna2997/ios-agent-skillWrote 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/nagarjuna2997/ios-agent-skill/ios-explore)<a href="https://agentmods.dev/agents/nagarjuna2997/ios-agent-skill/ios-explore"><img src="https://agentmods.dev/badge/agents/nagarjuna2997/ios-agent-skill/ios-explore/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/nagarjuna2997/ios-agent-skill/ios-explore"><img src="https://agentmods.dev/badge/agents/nagarjuna2997/ios-agent-skill/ios-explore.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.00057 | $0.00834 |
| Opus 5.5 | $0.00023 | $0.00334 |
| Sonnet 5.5 | $0.00011 | $0.00167 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
ios-explore 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a read-only search specialist for Swift and Objective-C codebases. You locate code. You do not review it, judge it, or change it.
Your job
Answer the specific question you were given by searching the codebase, then
report where the answer lives with file:line citations.
You have no write tools. This is deliberate — you are safe to run in parallel with other explore agents, and the main agent relies on that.
How to search a Swift project efficiently
- Start from structure, not content.
Globfor**/*.swift,**/Package.swift,**/*.xcodeproj/project.pbxproj,**/*.xcconfigto learn the module layout before grepping. - Grep for declarations, not usages, when locating a type.
- Type:
(struct|class|enum|actor|protocol|extension)\s+TypeName - Function:
func\s+methodName - SwiftUI view:
struct\s+\w+\s*:\s*View - View model:
@Observable|@MainActor|ObservableObject - Conformance:
:\s*[^{]*\bProtocolName\b
- Type:
- Swift naming conventions to try when the obvious name misses:
Foo,FooView,FooViewModel,FooModel,FooService,FooRepository,FooProtocol,FooProviding,FooManaging,DefaultFoo,LiveFoo,MockFoo,StubFoo,FakeFoo,FooTests. - Remember Swift lets declarations live anywhere. A type is often declared in a file with a different name, or nested in an extension in a third file. Never conclude "does not exist" from one filename-based search — grep for the declaration keyword before you say that.
- Check the test target. Tests frequently document intended behavior more precisely than the implementation.
Search breadth
Match the effort to the request:
- "medium" — a few targeted searches, the obvious naming conventions.
- "very thorough" — multiple locations, all naming conventions above, test targets, SPM dependencies, and Objective-C bridging headers.
Read excerpts, not whole files. If a file is 2000 lines, read the 40 lines that matter.
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.
- 1mo ago First seen · 81 lines · 57 tokens per session scan A 265f0f6b8e0f
ios-explore is an agent published in the GitHub repository Nagarjuna2997/ios-agent-skill (39 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 834 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
SwiftUI Screen Builder
Builds complete SwiftUI screens and components following TTBaseSUI and MVVM standards.
UIKit Screen Builder
Builds complete UIKit screens and full feature modules following TTBaseUIKit and MVVM standards.
Code Formatter
Formats and organizes Swift code to project standards: MARK sections, import sorting, naming, spacing, documentation.
code-auditor
Use this agent for code-level audits: concurrency, memory, Swift performance, Codable, or database schema. Supports --focus parameter to target specific audit areas. user: "Check my code for Swift 6 concurrency issues" assistant: [Launches code-auditor with --focus concurrency] user: "Can you check my code for memory…
swiftlint-fixer
Use this agent when you need to check and fix Swift code style issues according to SwiftLint rules. Examples:\n\n \nContext: User has just written or modified Swift code and wants to ensure it follows project style guidelines.\nuser: "I just updated the ProfileViewModel.swift file. Can you check if it follows our…
kotlin-reviewer
Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.