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/regression-tests/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/regression-tests)<a href="https://agentmods.dev/skills/telepresenceio/telepresence/regression-tests"><img src="https://agentmods.dev/badge/skills/telepresenceio/telepresence/regression-tests/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/regression-tests"><img src="https://agentmods.dev/badge/skills/telepresenceio/telepresence/regression-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 51 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 132 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00082 | $0.01608 |
| Opus 5 | $0.00041 | $0.00804 |
| Sonnet 5 | $0.00016 | $0.00322 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
regression-tests 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
regression-tests
Runs the telepresence regression suite from the main conversation, where this harness's shell-env quirks are known.
Background to assume
- Tests live under
regression_test/and need a working k8s cluster (kind / minikube / Docker Desktop) plus images it can reach. For a local cluster setRTEST_REGISTRY=localand LOAD the images into it rather than pushing. regression_test/README.mdis the reference: fixture-engine rules, the RTEST_* table, catalogs, labels, coverage. Read it before debugging a fixture problem.- The shell environment always wins; there is no config file. That means a
stale
exportin the user's shell silently changes a run.
Scoping: plain go test -run
Areas are ordinary Go tests, suites and methods are subtests, so one -run
expression selects at any depth:
go test ./regression_test -run '^TestIntercept$'
go test ./regression_test -run '^TestIntercept$/^HeaderFilter$'
go test ./regression_test -run '^TestIntercept$/^HeaderFilter$/^Test_PathPrefix$'
There is no TEST_SUITE/TEST_NAME indirection and no make-argument dance:
inline VAR=value prefixes work in this harness, so run go test directly
and keep make check-regression for the full unscoped suite.
Always pass -count=1 (results must never come from the test cache) and a
-timeout that fits the scope: minutes for one suite, -timeout=100m for a
full run.
The run command
TELEPRESENCE_REGISTRY=local TELEPRESENCE_VERSION=<version> \
RTEST_CONTEXT=<context> RTEST_TEARDOWN=1 \
go test -count=1 -timeout=30m -run '^TestArea$/^Suite$' ./regression_test \
> /tmp/rtest-suite.log 2>&1
RTEST_CONTEXTpins the kube context. Pin it explicitly whenever the machine has more than one cluster — the default is the kubeconfig's current context, which is onekubectxaway from being the wrong cluster.RTEST_TEARDOWN=1destroys the run's resources at the end. Without it, dev mode keeps namespaces, the release, and the connection for the next run to adopt, which is what makes a scoped rerun take seconds.RTEST_FRESH=1ignores adoptable resources (use when a previous run left something suspect). CI implies fresh + teardown.RTEST_LABELS/RTEST_SKIP_LABELSselect oncompat-core,slow,stress,flaky-retry.
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 · 135 lines · 82 tokens per session scan A 10a405f4e0fb
regression-tests is a skill published in the GitHub repository telepresenceio/telepresence (7,295 stars, last pushed yesterday), licensed Apache-2.0. It adds 82 tokens to every session and 1,608 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
starlark-dev
Develop and debug Kurtosis Starlark packages. Create packages from scratch, understand the plan-based execution model, use print() debugging, handle future references, and test packages locally. Use when writing or troubleshooting .star files.
cli-local-build
Build and test the Kurtosis CLI from source. Compile the CLI binary locally, run it against Docker or Kubernetes engines, and iterate on CLI changes without creating a release. Use when developing or debugging CLI commands.
reality-verification
This skill should be used when the user asks to "verify a fix", "reproduce failure", "diagnose issue", "check BEFORE/AFTER state", "VF task", "reality check", "check test quality", "mock-only tests", or needs guidance on verifying fixes by reproducing failures before and after implementation, or detecting mock-heavy…
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
quality-engineering-test-healing
Failure taxonomy and allowed/forbidden repairs for a failing E2E test. Use when a Playwright/Maestro/Detox/XCUITest/Espresso/Appium test fails and you must decide whether to repair the test or route to a real bug.