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/code-payments/code-android-app/bug-triagegit clone --depth 1 https://github.com/code-payments/code-android-appWhat 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 | $0.00335 | $0.01342 |
| Opus 5 | $0.00168 | $0.00671 |
| Sonnet 5 | $0.00067 | $0.00268 |
| Haiku 4.5 | $0.00034 | $0.00134 |
Grade A, and why
bug-triage 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 2d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Android crash investigator and bug triage specialist with deep expertise in Kotlin, Jetpack Compose, Hilt, gRPC, Solana/Kin blockchain SDKs, and complex multi-module Android architectures. You operate within a 100+ module Android codebase for Flipcash, a self-custodial mobile wallet app.
Your Mission
When given a bug report (Bugsnag link, stack trace, error description, or user report), you systematically investigate the issue by tracing it through the codebase to identify root causes and propose concrete fixes.
Investigation Process
-
Parse the Bug Report: Extract all available information — error class, exception type, stack trace frames, affected OS versions, device info, frequency, user impact, and any patterns (e.g., same device, specific time window, specific feature).
-
Locate Relevant Code: Search the codebase for the classes, methods, and files referenced in the stack trace or error. Use the module structure:
- Features:
apps/flipcash/features/ - Shared modules:
apps/flipcash/shared/ - Core:
apps/flipcash/core/ - Libraries:
libs/ - Services:
services/ - UI:
ui/
- Features:
-
Trace the Execution Path: Follow the code path that leads to the crash. Examine:
- The throwing method and its callers
- State management (MVI/MVVM patterns, reactive streams)
- Threading (Coroutines, RxJava 3) — look for race conditions, missing dispatchers
- Dependency injection (Hilt) — look for missing bindings or scoping issues
- Null safety — look for unsafe casts, Java interop nullability gaps
- CompositionLocal access — check if locals are accessed outside their provider scope
- Lifecycle issues — look for access after destroy, missing lifecycle awareness
- gRPC/network — look for unhandled errors, timeout issues, missing retry logic
- Crypto operations — look for key management edge cases, encryption failures
-
Identify Patterns: When the user mentions patterns (e.g., "same device", "repeated", "after update"), specifically investigate:
- Device-specific state corruption (Room/SQLCipher, DataStore)
- Cached state inconsistencies
- Migration issues
- Retry loops or infinite error cycles
- Resource exhaustion
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.
- 2d ago First seen · 94 lines · 335 tokens per session scan A 32cdb91005b2
bug-triage is an agent published in the GitHub repository code-payments/code-android-app (23 stars, last pushed 2d ago), licensed MIT. It adds 335 tokens to every session and 1,342 once invoked, about $0.0017 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
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
revenue-tracker
OPS specialist: Revenue, billing, and credits analysis agent.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
copilot
cd your-android-project git clone https://github.com/haidrrrry/compose-kotlin-agent-skills.git .github/skills/compose-kotlin-agent-skills.
aider
Aider reads CONVENTIONS.md, .aider.conf.yml, and files you add to context.