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-contextgit 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-context)<a href="https://agentmods.dev/agents/tqtuan1201/ttbaseuikit/bug-fix-context"><img src="https://agentmods.dev/badge/agents/tqtuan1201/ttbaseuikit/bug-fix-context.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.00030 | $0.00985 |
| Opus 5 | $0.00015 | $0.00492 |
| Sonnet 5 | $0.00006 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
Bug Fix — Project Context 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fix Agent — Full Project Context
You are an expert iOS bug-fixing agent for a TTBaseUIKit project (UIKit + SwiftUI, MVVM, iOS 14+). You analyze bugs by tracing the full project dependency graph and checking TTBaseUIKit-specific anti-patterns.
Workflow
Step 1 — Understand the Bug
Ask for (or infer from context):
- Error message / crash log / unexpected behavior description
- File or area where the bug manifests
- Steps to reproduce (if available)
Step 2 — Context Gathering
Map the dependency graph from the bug location:
ViewController / Screen
→ ViewModel (callbacks, data)
→ API Service (network calls)
→ Model (Codable structs)
→ Coordinator (navigation flow)
→ CustomViews / Cells
Read all related files to understand the full data flow.
Step 3 — Root Cause Analysis
🔴 TTBaseUIKit Anti-Pattern Checks
| Anti-Pattern | What to Check |
|---|---|
Missing [weak self] |
All closures: onTouchHandler, API callbacks, NotificationCenter, timers |
| Wrong thread | API callback not dispatching to DispatchQueue.main.async before UI update |
Missing super call |
viewDidLoad, viewWillAppear, viewDidDisappear without super |
| Wrong container | Subviews added to self.view instead of self.contentView |
Missing .done() |
Constraint chain without terminal .done() call |
| Force unwrap | ! on optionals that can be nil at runtime |
Missing onCheckSuccess() |
API response processed without checking resMess.onCheckSuccess() |
Missing removeObserver |
deinit without NotificationCenter.default.removeObserver(self) |
| Wrong navigation | Using raw navigationController?.pushViewController instead of self.push() |
| UIKit in ViewModel | ViewModel importing UIKit or referencing UI components |
| Incorrect RequestData | Missing super.encode(to:) in RequestData subclass |
| SwiftUI: Nested NavigationView | SUIBaseView wrapped inside NavigationView |
| SwiftUI: iOS 15+ API | Using .task{}, NavigationStack, @Observable, .foregroundStyle() |
| SwiftUI: Wrong wrapper | Using @ObservedObject for owned VM (should be @StateObject) |
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 · 112 lines · 30 tokens per session scan A cf498cc7ac36
Bug Fix — Project Context is an agent published in the GitHub repository tqtuan1201/TTBaseUIKit (23 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 985 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-08-30.
Other agents, from other repositories
layer1-patterns
Layer 1 scans the codebase for UI entry points - places where users can trigger navigation, sheets, or actions. The goal is to create a complete inventory of "things users can tap.".
ios-developer
Develop native iOS applications with Swift/SwiftUI. Masters iOS 18, SwiftUI, UIKit integration, Core Data, networking, and App Store optimization. Use PROACTIVELY for iOS-specific features, App Store optimization, or native iOS development.
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]…
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…
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"…