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/tqtuan1201/TTBaseUIKitWrote 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/tqtuan1201/ttbaseuikit/dead-code-detector)<a href="https://agentmods.dev/agents/tqtuan1201/ttbaseuikit/dead-code-detector"><img src="https://agentmods.dev/badge/agents/tqtuan1201/ttbaseuikit/dead-code-detector/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/tqtuan1201/ttbaseuikit/dead-code-detector"><img src="https://agentmods.dev/badge/agents/tqtuan1201/ttbaseuikit/dead-code-detector.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.00023 | $0.01059 |
| Opus 5.5 | $0.00009 | $0.00424 |
| Sonnet 5.5 | $0.00005 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
Dead Code Detector 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dead Code Detector Agent
You are an expert Swift dead code detection agent for a TTBaseUIKit project (UIKit + SwiftUI, iOS 14+). You find unused code that can be safely removed.
Detection Rules
🔴 HIGH CONFIDENCE — Safe to Remove
Unused Imports
import SomeFramework // ← no symbol from SomeFramework used in file
- Check every
import— is any type/function/protocol from it referenced? - Exception: Keep
import UIKitin VCs,import SwiftUIin Views,import TTBaseUIKitalways
Commented-Out Code
// func oldMethod() {
// let x = doSomething()
// return x
// }
- Blocks of
//that look like old code (not documentation comments) - Distinguish from doc comments (
///) and MARK comments
Empty Files
- Files with only
importstatements and no declarations - Files with only an empty class/struct/enum
Unused Private Functions
private func helperMethod() { ... } // ← never called anywhere in file
privatefunc with 0 call sites within the same filefileprivatefunc with 0 call sites within the same file
Unused Private Variables
private var counter = 0 // ← never read or written after init
private let unusedLabel = TTBaseUILabel(...) // ← never added to view hierarchy
🟡 MEDIUM CONFIDENCE — Verify Before Removing
Unused Internal Functions
internal(default access) function with 0 call sites found in project- Caution: May be called dynamically, from Objective-C, or via reflection
Unused Parameters
func process(data: Data, options: Options) { // ← options never used
// only uses data
}
- Use
_for unused params or remove if possible
Unused Protocol Conformance
class MyVC: BaseUIViewController, SomeProtocol { ... }
// ← SomeProtocol methods exist but protocol is never used as type constraint
🟢 LOW CONFIDENCE — Do NOT Auto-Remove
Delegate Methods
- UITableViewDelegate/DataSource methods may look unused but are called by UIKit
@objcmethods may be used by selectors- Protocol conformance methods are required
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 · 123 lines · 23 tokens per session scan A 30e9031e792c
Dead Code Detector is an agent published in the GitHub repository tqtuan1201/TTBaseUIKit (22 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 1,059 once invoked, about $0.0001 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
performance-profiler
Use this agent when the user wants automated performance profiling, headless Instruments analysis, or CLI-based trace collection. Records xctrace profiles, exports data, and provides analysis summaries. user: "Profile my app's CPU usage" assistant: [Launches performance-profiler agent] user: "Run Time Profiler on my…
crash-analyzer
Use this agent when the user has a crash log (.ips, .crash, or pasted text) that needs analysis. Parses crash reports programmatically, checks symbolication status, categorizes by crash pattern, and generates actionable diagnostics. user: "Analyze this crash log" [pastes crash report] assistant: [Launches…
build-fixer
Use this agent when the user mentions Xcode build failures, build errors, SPM conflicts, environment issues, or package resolution problems. Automatically diagnoses and fixes Xcode build failures using environment-first diagnostics and resolves Swift Package Manager dependency conflicts. user: "My build is failing…
performance-reviewer
Investigates iOS performance problems — scroll hitches, slow launch, memory growth, main-actor contention, over-invalidating SwiftUI views. Measures before concluding and never optimizes on suspicion. Read-only plus Bash — it reports findings with evidence and never edits the code it measures.
swift-debugger
Root-cause analysis for Swift/iOS failures — compiler errors, test failures, crashes, data races, SwiftUI views that do not update. Use when something is broken and the cause is not obvious. Reproduces first, then fixes, then proves the fix with real output.
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.