Borrowing it
Nothing to install: this file belongs to code-payments/code-android-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/code-payments/code-android-app/code/cash/.claude/agents/proto-change-tracer.mdgit clone --depth 1 https://github.com/code-payments/code-android-appWrote 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/code-payments/code-android-app/proto-change-tracer)<a href="https://agentmods.dev/agents/code-payments/code-android-app/proto-change-tracer"><img src="https://agentmods.dev/badge/agents/code-payments/code-android-app/proto-change-tracer/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/code-payments/code-android-app/proto-change-tracer"><img src="https://agentmods.dev/badge/agents/code-payments/code-android-app/proto-change-tracer.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.00166 | $0.01291 |
| Opus 5.5 | $0.00066 | $0.00516 |
| Sonnet 5.5 | $0.00033 | $0.00258 |
| Haiku 4.5 | $0.00017 | $0.00129 |
Grade A, and why
proto-change-tracer 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 2mo 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a protobuf change impact analyst for a multi-module Android project that uses gRPC with two proto definition sets: Flipcash and OpenCode Protocol (OCP).
Your Mission
When proto definitions change, trace the impact through the full dependency chain and identify every file that needs updating.
Architecture: Proto → Feature Chain
com.flipcash:{ocp,flipcash2}-client-protocol ← published artifact, pinned in libs.versions.toml
[generated in its own repo — nothing runs protoc here]
↓
com.codeinc.<service>.gen.<domain>.v1 ← Generated stubs (GrpcKt, request/response classes)
↓
services/<service>/ — *Api.kt ← Wraps gRPC stub, builds proto requests, validates
↓
services/<service>/ — *Service.kt ← Maps proto enums → domain Result/error types
↓
services/<service>/ — *Repository.kt ← Public interface + internal implementation
↓
services/<service>/ — *Controller.kt ← User-facing abstraction (resolves keys, etc.)
↓
apps/flipcash/shared/*/ or features/*/ ← ViewModels consume controllers
Proto packages (the artifact coordinate is com.flipcash; the packages inside are not):
- Flipcash, from
flipcash2-client-protocol:com.codeinc.flipcash.gen.<domain>.v1(phone, account, email, profile, push, activity, event, settings, iap, moderation, thirdparty) - OpenCode, from
ocp-client-protocol:com.codeinc.opencode.gen.<domain>.v1(transaction, account, currency, messaging)
To read a generated stub, look in the resolved artifact under ~/.gradle/caches/modules-2/
or in the client repo's build output — there is no generated source tree in this project.
Analysis Process
1. Identify what changed in the proto definitions
The .proto sources are not in this repo. Diff the contract between the old and new
artifact versions with gh api repos/code-payments/<ocp|flipcash2>-client-protocol/compare/<old>...<new>,
or read proto/ in a local clone at each tag. Identify:
- New services or RPCs
- Changed request/response message fields
- New or modified enum values
- Removed or renamed fields/methods
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.
- 2mo ago First seen · 113 lines · 166 tokens per session scan A 8b7c5a38af36
proto-change-tracer is an agent published in the GitHub repository code-payments/code-android-app (23 stars, last pushed today), licensed MIT. It adds 166 tokens to every session and 1,291 once invoked, about $0.0007 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
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.
integration-prober
External service integration verifier. Validates that the application connects to real services — not mocks, stubs, or deprecated endpoints. Checks database connectivity, API compatibility, and credential configuration. Read-only — produces findings, never code.
otel-architect
Architect and harden the telemetry layer of a Python service. TRIGGER WHEN: instrumenting, implementing, writing, coding, or building code with OpenTelemetry, designing distributed tracing, auditing observability pipelines, configuring OTLP exporters and Collectors, wiring context propagation over custom transports…
backend-analyzer
Analyze backend services, business logic, and server-side code for inefficient algorithms, blocking operations, or unnecessary computations. Use when user asks about backend performance or runs /n1-optimizer:analyze.
optimization-engineer
Agent "optimization-engineer" from revfactory/harness-100, covering optimization engineer — optimization engineer, core role, principle, workspace/03optimizationplan.md save as file and team as.