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/AGENTS.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/instructions/telepresenceio/telepresence/agents-md)<a href="https://agentmods.dev/instructions/telepresenceio/telepresence/agents-md"><img src="https://agentmods.dev/badge/instructions/telepresenceio/telepresence/agents-md.svg" alt="Measured on agentmods" 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.04458 | $0.04458 |
| Opus 5 | $0.02229 | $0.02229 |
| Sonnet 5 | $0.00892 | $0.00892 |
| Haiku 4.5 | $0.00446 | $0.00446 |
Grade B, and why
telepresence AGENTS.md scanned grade B with 1 finding 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 8d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo telepresence rootd --logfile - --address :8084 How it starts
The opening of the file, as written. The whole thing — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance for contributors and AI assistants working with this repository.
Project Overview
Telepresence is a Kubernetes development tool that enables fast local development by connecting your local workstation to a Kubernetes cluster. It allows developers to run services locally while accessing cluster resources and intercepting traffic from the cluster to their local machine.
Git Workflow
- Never commit directly to the
release/v2branch. Always create a feature branch with a name following the patternusername/topic(e.g.,thallgren/fix-dns-resolution). - All commits must be signed and signed-off (
git commit -s -S). - Limit commit message subjects to 72 characters. Do not wrap subjects; rewrite them shorter instead. Wrap commit message body lines at 72 characters by default unless preserving exact external text requires a longer line.
- Always run
make lintand fix every reported issue before pushing. This is non-negotiable — CI runs the same linters and a push with lint errors wastes a CI cycle. Ifmake lintfinds problems, fix them in the appropriate commit (usegit commit --fixup=<sha>followed byGIT_SEQUENCE_EDITOR=: git rebase -i --autosquash --gpg-sign <base>to fold them in) before pushing. - Push the branch and create a pull request for review.
- Always merge PRs with a merge commit (never squash or rebase).
Design Plans
Major work (multi-file changes, new features, refactors) starts with a written plan
under docs/plans/<topic>/, presented for review before implementation begins.
A plan is scaffolding for review, not a lasting artifact. It is removed in the last commit on the PR that implements it. By then, everything in the plan must have been implemented and documented, so the plan no longer has a purpose.
Build Artifacts
The Open Source version of Telepresence consists of three artifacts:
Client-side (runs on developer workstation):
telepresencebinary - The same binary serves as CLI, user daemon, and root daemon.telepresenceDocker image - Used as both user and root daemon when runningtelepresence connect --docker.
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.
- 8d ago First seen · 446 lines · 4,458 tokens per session scan B 90ceb1e402c1
telepresence AGENTS.md is an instructions file published in the GitHub repository telepresenceio/telepresence (7,293 stars, last pushed 13d ago), licensed Apache-2.0. It adds 4,458 tokens to every session, about $0.0223 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.