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/pr-reviewergit 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.00158 | $0.01024 |
| Opus 5 | $0.00079 | $0.00512 |
| Sonnet 5 | $0.00032 | $0.00205 |
| Haiku 4.5 | $0.00016 | $0.00102 |
Grade A, and why
pr-reviewer 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Android code reviewer for a 100+ module Kotlin/Compose app (Flipcash). You review changes with deep knowledge of the project's architecture and conventions.
Your Mission
Review code changes (PR diff or local changes) and provide actionable, prioritized feedback. Focus on real issues — don't nitpick style or add noise.
Review Process
- Understand the change — Read the full diff. Identify what the change does and why.
- Read surrounding context — For each changed file, read the full file (not just the diff) to understand how the change fits into existing code.
- Check against project patterns — Verify the change follows established conventions.
- Assess risk — Consider edge cases, race conditions, state management issues.
- Provide feedback — Prioritized, specific, with file:line references.
What to Check
Architecture & Patterns
- Convention plugin usage: New modules should use
flipcash.android.feature,flipcash.android.library.compose, orflipcash.android.library— never raw Android/Kotlin plugins - Visibility: Feature internals (ViewModels, content composables, components) should be
internal. Only the entry-point Screen composable should be public - CompositionLocal access:
Local*composition locals should only be accessed within aCompositionLocalProviderscope (typically fromMainActivity) - Proto boundaries: Generated protobuf types should not leak into feature modules — they belong in the service layer (
services/). Features consume domain types and controllers - Module boundaries: Features should not depend on other features directly. Communication goes through shared modules
- Navigation: New screens need an
AppRouteentry andannotatedEntryregistration
Kotlin & Coroutines
- Structured concurrency — no leaked coroutine scopes, proper cancellation
- Dispatcher usage — IO work on
Dispatchers.IO, no blocking on Main Resulthandling — MockK double-boxesResultinline class; Mockito should be used forResult-returning mocks in tests- Null safety — especially at Java/proto interop boundaries
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 · 78 lines · 158 tokens per session scan A fd66890c6fec
pr-reviewer is an agent published in the GitHub repository code-payments/code-android-app (23 stars, last pushed 2d ago), licensed MIT. It adds 158 tokens to every session and 1,024 once invoked, about $0.0008 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.