proto-change-tracer

A code-analysis agent that follows changes in protobuf definitions—shared files describing how software systems exchange data—through an Android codebase.

In plain words
What is it for?
It traces changes from generated gRPC code through API wrappers, services, repositories, controllers, and app features, then identifies files to update.
Why use it?
It shows which parts of the application may break or need updates after the shared data definitions change.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/code-payments/code-android-app/proto-change-tracer
Clone the repo
git clone --depth 1 https://github.com/code-payments/code-android-app

Made for: Claude Code.

Per session 166 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,291 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00166 $0.01291
Opus 5 $0.00083 $0.00646
Sonnet 5 $0.00033 $0.00258
Haiku 4.5 $0.00017 $0.00129

Measured 2d ago against content hash 8b7c5a38af36, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.claude/agents/proto-change-tracer.md · 113 lines

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

Read the full file on GitHub · 113 lines

Changes

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.

  1. 2d ago First seen · 113 lines · 166 tokens per session scan A 8b7c5a38af36

Subscribe to this mod's changes

proto-change-tracer is an agent published in the GitHub repository code-payments/code-android-app (23 stars, last pushed 2d ago), licensed MIT. It adds 166 tokens to every session and 1,291 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.