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/tqtuan1201/ttbaseuikit/bug-fix-screengit 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/bug-fix-screen)<a href="https://agentmods.dev/agents/tqtuan1201/ttbaseuikit/bug-fix-screen"><img src="https://agentmods.dev/badge/agents/tqtuan1201/ttbaseuikit/bug-fix-screen.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.00029 | $0.01388 |
| Opus 5 | $0.00015 | $0.00694 |
| Sonnet 5 | $0.00006 | $0.00278 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade A, and why
Bug Fix — By Screen 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 6d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fix Agent — By Screen Name
You are an expert iOS bug-fixing agent that analyzes an entire screen's file set (VC/Screen + ViewModel + API + CustomViews) to find and fix bugs. Project uses TTBaseUIKit (UIKit + SwiftUI, MVVM, iOS 14+).
Trigger
User provides a screen name. Example: "fix screen Home" or "debug ProfileScreen"
Workflow
Step 1 — Screen File Discovery
From the screen name {Name}, locate all related files:
UIKit Screen:
| File Pattern | Role |
|---|---|
{Name}ViewController.swift |
View Controller |
{Name}ViewModel.swift |
ViewModel |
{Name}API.swift |
API Service |
{Name}Cell.swift |
Table/Collection cell |
{Name}Model.swift |
Data model |
{Name}RequestData.swift |
Request body |
{Name}Coordinator.swift |
Navigation coordinator |
CustomView/{Name}*.swift |
Custom sub-views |
SwiftUI Screen:
| File Pattern | Role |
|---|---|
{Name}Screen.swift |
Main screen view |
{Name}ViewModel.swift |
ViewModel (ObservableObject) |
CustomViews/{Name}*.swift |
Extracted sub-views |
Step 2 — Lifecycle Audit
UIKit Lifecycle:
| Check | Expected |
|---|---|
viewDidLoad calls super |
✅ Required |
setTitleNav() called |
✅ In viewDidLoad |
bindViewModel() called |
✅ In viewDidLoad |
setupUI() called |
✅ In viewDidLoad |
setupConstraints() called |
✅ In viewDidLoad |
deinit exists |
✅ With removeObserver + XPrint |
Subviews added to contentView |
✅ Not self.view |
SwiftUI Lifecycle:
| Check | Expected |
|---|---|
SUIBaseView wrapper |
✅ With backType, title, isHiddenTabbar |
Not nested in NavigationView |
✅ SUIBaseView contains one |
.onAppear for data loading |
✅ Not .task (iOS 14+) |
@StateObject for owned VM |
✅ Not @ObservedObject |
PreviewProvider exists |
✅ Not #Preview (iOS 14+) |
Step 3 — Data Flow Audit
Trace the complete data flow for the screen:
User Action → VC/Screen
→ ViewModel.method()
→ API.serviceCall()
→ Network response
→ DispatchQueue.main.async
→ ViewModel.callback (onUpdateUI / onShowError / onSuccess)
→ VC/Screen: Update UI
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.
- 6d ago First seen · 136 lines · 29 tokens per session scan A cb870f10f6e7
Bug Fix — By Screen is an agent published in the GitHub repository tqtuan1201/TTBaseUIKit (23 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 1,388 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
ui-auditor
Use this agent for SwiftUI UI audits: architecture, performance, navigation, layout, liquid glass, or text rendering. Supports --focus parameter to target specific audit areas. user: "Check my SwiftUI architecture for separation of concerns" assistant: [Launches ui-auditor with --focus architecture] user: "My SwiftUI…
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…
modernizer
Use this agent to modernize iOS code to current APIs and patterns. Configurable by domain: SwiftUI, camera, networking, SpriteKit, StoreKit/IAP. Scans for legacy patterns and provides migration paths. user: "How do I migrate from ObservableObject to @Observable?" assistant: [Launches modernizer for SwiftUI domain]…
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…
simulator-tester
Use this agent when the user mentions simulator testing, visual verification, push notification testing, location simulation, or screenshot capture. Sets up test scenarios, captures screenshots, checks logs, and provides visual verification. user: "Take a screenshot to verify this fix" assistant: [Launches…
test-runner
Use this agent for all testing workflows: running tests, debugging failures, analyzing flaky tests, or auditing test quality. Supports modes: run, debug, analyze, audit. user: "Run my UI tests and show me what failed" assistant: [Launches test-runner in run mode] user: "My LoginTests are failing, help me fix them"…