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/skills/ship-release/SKILL.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/skills/telepresenceio/telepresence/ship-release)<a href="https://agentmods.dev/skills/telepresenceio/telepresence/ship-release"><img src="https://agentmods.dev/badge/skills/telepresenceio/telepresence/ship-release/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/skills/telepresenceio/telepresence/ship-release"><img src="https://agentmods.dev/badge/skills/telepresenceio/telepresence/ship-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.02956 |
| Opus 5 | $0.00036 | $0.01478 |
| Sonnet 5 | $0.00014 | $0.00591 |
| Haiku 4.5 | $0.00007 | $0.00296 |
Grade A, and why
ship-release 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 10d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ship-release
End-to-end driver for releasing Telepresence. Picks up where prepare-release left off and carries the change through:
- Telepresence release PR (CI green +
regressiongreen) - Docs PR in
../telepresence.io - Tag push, Releases workflow, merge of both PRs.
This is user-only (disable-model-invocation: true). A release is publicly visible and partially irreversible (tags push to GitHub, Homebrew updates for GA). Claude must never invoke this on its own.
Preconditions to verify before doing anything
Run each check and stop with a clear message if any fails:
- CWD is the telepresence repo.
git rev-parse --show-toplevelends intelepresence. make prepare-releasehas been run. The current HEAD must carry bothvX.Y.Zandrpc/vX.Y.Zannotated tags locally:
Two entries expected. If the tag list is empty or missing thegit tag --points-at HEAD | sortrpc/peer, stop — the user needs to runmake prepare-releasefirst.- Branch is pushed. Capture
tp_branch=$(git branch --show-current), then:
If this fails, stop and tell the user to push the branch first.git ls-remote --exit-code origin "refs/heads/$tp_branch" - PR exists.
gh pr view "$tp_branch" --json number,state,url,headRefName. If no PR, stop. - Sibling docs repo present.
test -d ../telepresence.io && test -d ../telepresence.io/.git. If not, stop.
Capture once and reuse throughout:
tp_branch— name of the prepare-release branch.tp_version— pick the non-rpc/tag fromgit tag --points-at HEAD(e.g.v2.28.0).docs_version—echo "$tp_version" | sed -E 's/^v([0-9]+\.[0-9]+).*/\1/'(e.g.2.28).pr_number— fromgh pr view.
Phase 1 — Drive the Telepresence release PR
1.1 Verify branch and PR (already done in preconditions)
1.2 Wait for all checks except regression to be green
Use:
gh pr checks "$tp_branch" --json name,state,conclusion
Filter out the rows whose name is exactly regression or node_agent_docker_runtime (neither has been triggered yet — the label triggers them). Match the name exactly: regression_compat is a different job, and it only runs behind the compatibility test label. For every remaining row:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 253 lines · 72 tokens per session scan A 26d533a8615e
ship-release is a skill published in the GitHub repository telepresenceio/telepresence (7,295 stars, last pushed yesterday), licensed Apache-2.0. It adds 72 tokens to every session and 2,956 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 skills, from other repositories
publish-plugins
(project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests.
pr
Use when the user explicitly asks to push the current branch and open a PR, rewrite an open PR's body from its commits, or wait for CI and merge it.
maintainer-ops
Use for vLLM Semantic Router issue intake, PR decisions, releases, and reviewed GitHub mutations performed on behalf of maintainers.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
create-release
Create a versioned GitHub release with changelog.
commit
Use when making any git commit. Always pass why the changes were made as the argument; when no reason was stated, pass the request that prompted the changes instead — never an invented why.