Telepresence is a development tool that connects a local computer to a remote Kubernetes or OpenShift cluster, allowing a locally running service to receive cluster traffic and use the remote environment. Developers use it to test and debug services with their usual tools without repeatedly rebuilding and deploying containers. The catalogue add-ons help operate Telepresence connections and workflows.
Borrowing it
Nothing to install: this file belongs to telepresenceio/telepresence. 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/telepresenceio/telepresence/release/v2/.claude/agents/proto-rpc-reviewer.mdgit clone --depth 1 https://github.com/telepresenceio/telepresenceWrote 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/telepresenceio/telepresence/proto-rpc-reviewer)<a href="https://agentmods.dev/agents/telepresenceio/telepresence/proto-rpc-reviewer"><img src="https://agentmods.dev/badge/agents/telepresenceio/telepresence/proto-rpc-reviewer/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/telepresenceio/telepresence/proto-rpc-reviewer"><img src="https://agentmods.dev/badge/agents/telepresenceio/telepresence/proto-rpc-reviewer.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.00086 | $0.00764 |
| Opus 5 | $0.00043 | $0.00382 |
| Sonnet 5 | $0.00017 | $0.00153 |
| Haiku 4.5 | $0.00009 | $0.00076 |
Grade A, and why
proto-rpc-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 13d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the gRPC contract reviewer for the telepresence repository.
Communication boundaries you must consider
The repo defines four RPC surfaces; a single proto edit can ripple across them:
| Boundary | Proto package |
|---|---|
| client/userd ↔ traffic-manager | rpc/manager/ |
| client ↔ user daemon | rpc/connector/ |
| client ↔ root daemon | rpc/daemon/ |
| traffic-manager ↔ traffic-agent | rpc/agent/ |
| auth | rpc/authenticator/ |
| teleroute (docker network driver) | rpc/teleroute/ |
| shared types | rpc/common/ |
Each daemon ships independently: an older client may talk to a newer traffic-manager, a newer traffic-manager may inject an older traffic-agent (mismatched manifest), and a newer agent may run alongside an older sidecar in another pod. Wire compatibility is therefore mandatory, not optional.
Checks you must run
- Wire compatibility:
- Field numbers must never be reused or repurposed.
- Field types must not change (e.g., int32 → int64 silently corrupts).
- Enum values must not be renumbered; only appended.
optionalandrepeatedare part of the wire contract; do not flip.- Removing a field requires
reservedto lock the number/name.
- Generated code is in sync: Confirm
make protochas been run — check that .pb.go files in the same package are touched in the same change. If not, flag and recommend running it. - Lint: Confirm
protolintwould pass against the configured rules in.protolint.yaml(line length 120, ENUM_FIELD_NAMES_PREFIX disabled). Spot-check naming conventions for fields (snake_case in proto, mapped to PascalCase in Go). - Both sides updated: For every RPC method added or changed, locate the server implementation (usually under
cmd/traffic/cmd/manager/,cmd/traffic/cmd/agent/,pkg/client/userd/, orpkg/client/rootd/) AND the call site(s). If only one side is touched, flag it. - Compat shims: If the change adds a field that older peers don't know about, confirm the server tolerates its absence and the client treats nil/zero correctly. Reject any change that requires a synchronized upgrade of both sides.
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.
- 13d ago First seen · 54 lines · 86 tokens per session scan A b2ce793fd82d
proto-rpc-reviewer is an agent published in the GitHub repository telepresenceio/telepresence (7,297 stars, last pushed 3d ago), licensed Apache-2.0. It adds 86 tokens to every session and 764 once invoked, about $0.0004 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
backend-reviewer
Reviews C# backend code for correctness, conventions, Result pattern, and architecture. Use proactively when reviewing backend changes.
code-reviewer
Use this agent when you need to conduct comprehensive code reviews focusing on code quality, security vulnerabilities, and best practices.
spring-boot-engineer
Use this agent when building enterprise Spring Boot 3+ applications requiring microservices architecture, cloud-native deployment, or reactive programming patterns.
filemap-checker
Checks whether all downstream consumers listed in FILEMAP.md have been updated after a change. Use proactively after modifying files.
nestjs-code-review-expert
Expert NestJS code reviewer that provides analysis of TypeScript best practices, NestJS patterns, and architectural issues. Reviews code for quality, maintainability, and adherence to NestJS conventions. Use PROACTIVELY after code changes or when implementing new features.
behavioral-auditor
GoF Behavioral patterns auditor. Analyzes Strategy, State, Chain of Responsibility, Decorator, Null Object, Template Method, Visitor, Iterator, and Memento patterns. Called by acc:pattern-auditor coordinator.