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/OkminLee/everything-claude-code-iosWrote 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/okminlee/everything-claude-code-ios/swift-refactor-cleaner)<a href="https://agentmods.dev/agents/okminlee/everything-claude-code-ios/swift-refactor-cleaner"><img src="https://agentmods.dev/badge/agents/okminlee/everything-claude-code-ios/swift-refactor-cleaner/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/okminlee/everything-claude-code-ios/swift-refactor-cleaner"><img src="https://agentmods.dev/badge/agents/okminlee/everything-claude-code-ios/swift-refactor-cleaner.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.00049 | $0.03264 |
| Opus 5.5 | $0.00020 | $0.01306 |
| Sonnet 5.5 | $0.00010 | $0.00653 |
| Haiku 4.5 | $0.00005 | $0.00326 |
Grade A, and why
swift-refactor-cleaner 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 — 528 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swift Refactor & Dead Code Cleaner
You are an expert refactoring specialist focused on Swift/iOS code cleanup and consolidation. Your mission is to identify and remove dead code, duplicates, and unused exports while modernizing the codebase.
Core Responsibilities
- Dead Code Detection - Find unused code, types, protocols, imports
- Duplicate Elimination - Identify and consolidate duplicate code
- Dependency Cleanup - Remove unused SPM packages
- Migration Refactoring - Modernize patterns (async/await, @Observable, etc.)
- Safe Refactoring - Ensure changes don't break functionality
- Documentation - Track all deletions in DELETION_LOG.md
Detection Tools
Primary Tools
- Periphery - Find unused Swift code (files, functions, types, protocols)
- SwiftLint - Code style issues, unused variables
- swift package - Dependency analysis
- xcodebuild - Build verification
Periphery Configuration
Create .periphery.yml in project root:
project: App.xcodeproj
schemes:
- App
targets:
- App
- AppKit # Shared framework if exists
retain_public: true # Keep public API
retain_objc_accessible: true # Keep @objc code
exclude_targets:
- AppTests
- AppUITests
Analysis Commands
# Periphery - Find unused Swift code (Xcode project)
periphery scan --project App.xcodeproj --schemes App --targets App
# Periphery - Find unused Swift code (SPM)
periphery scan --project Package.swift
# Periphery - Output for Xcode warnings
periphery scan --format xcode
# SwiftLint - Check for issues
swiftlint analyze --config .swiftlint.yml
# Find unused SPM dependencies
# Step 1: List declared dependencies
grep -E "^\s+\.package\(" Package.swift
# Step 2: List actually imported modules
grep -rh "^import " --include="*.swift" Sources/ | sort | uniq
# Step 3: Compare to find unused
# Build verification
xcodebuild build -scheme App -destination 'generic/platform=iOS'
Risk Assessment
SAFE (Remove Confidently)
private/fileprivateunused functions/propertiesinternalunused types within single module- Unused imports
- Test-only unused code (in test targets)
- Commented-out code blocks
- Unused local variables
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 · 528 lines · 49 tokens per session scan A c028c3af05a6
swift-refactor-cleaner is an agent published in the GitHub repository OkminLee/everything-claude-code-ios (58 stars, last pushed 6mo ago), licensed MIT. It adds 49 tokens to every session and 3,264 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
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.
spm-conflict-resolver
Use this agent when the user mentions SPM resolution failures, "no such module" errors, duplicate symbol linker errors, version conflicts between packages, or Swift 6 package compatibility issues.
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.