mirrord lets a program running on a developer’s machine behave as though it were running inside a selected pod in a Kubernetes cluster, by routing the pod’s environment, files, network, and traffic to the local process. Developers and AI coding agents use it to build and test against live cluster services without deploying or disrupting other users; the catalogue entries provide instructions for using it.
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.
npx skills add metalbear-co/mirrord --skill mirrord-prev-envgit clone --depth 1 https://github.com/metalbear-co/mirrordWrote 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/metalbear-co/mirrord/mirrord-prev-env)<a href="https://agentmods.dev/skills/metalbear-co/mirrord/mirrord-prev-env"><img src="https://agentmods.dev/badge/skills/metalbear-co/mirrord/mirrord-prev-env/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/metalbear-co/mirrord/mirrord-prev-env"><img src="https://agentmods.dev/badge/skills/metalbear-co/mirrord/mirrord-prev-env.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.00122 | $0.08596 |
| Opus 5.5 | $0.00049 | $0.03438 |
| Sonnet 5.5 | $0.00024 | $0.01719 |
| Haiku 4.5 | $0.00012 | $0.00860 |
Grade A, and why
mirrord-prev-env scanned grade A 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Reaching a preview** requires sending the filter header (e.g. `baggage: mirrord-session=<key>`). Developers can inject it with the [mirrord Browser Extension](https://metalbear.com/mirrord/docs/using-mirrord/incoming How it starts
The opening of the file, as written. The whole thing — 509 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mirrord Preview Environment Skill
Purpose
Help users create and manage mirrord preview environments. A preview environment runs only the modified service(s) as isolated pods in a shared cluster, while their dependencies reach the rest of the main cluster through mirrord. Traffic is scoped by an environment key and a filter, so a change can be collaborated on, validated, and reviewed against real traffic without affecting live services.
This skill covers two modes:
- Ad-hoc (developer) mode — a developer runs the
mirrord previewCLI (start/status/stop) directly. - CI mode — the
metalbear-co/mirrord-previewGitHub Action wires previews into a PR lifecycle (start on open/push, stop on close).
When to Use This Skill
Trigger on questions like:
- "How do I run a mirrord preview environment?"
- "Set up per-PR preview environments with mirrord"
- "How do I use the mirrord-preview GitHub Action?"
- "
mirrord preview start— what config and flags do I need?" - "How do I route only my traffic to the preview pod?"
- "How do I check / stop a preview session?"
Security (must follow)
Preview environments deploy an image into a shared cluster and route live traffic to it, so the security bar is higher than for config generation. Always:
- Never instruct or generate remote pipe-to-shell installs (downloading a script and executing it via the shell) or similar patterns to install mirrord. If the user needs the CLI, point them to the official mirrord installation docs and their org's approved install path. In CI, pre-install mirrord in a trusted runner image or pin a verified release.
- Only deploy images you trust. A preview runs an arbitrary container image inside your cluster. In CI, do not auto-start previews for pull requests from forks — that would execute untrusted contributor code against your real cluster. Gate
starton same-repo PRs (e.g. checkpull_request.head.repo.full_name == <owner>/<repo>) or trusted authors, as the reference playground workflow does. - Scope the traffic filter narrowly.
stealmode intercepts matching requests away from the real target. Key theheader_filterto a unique environment key so a preview can never capture another session's or production's traffic. Prefer the more conservativemirrormode when you only need to observe. - Target staging, not production. Previews are for shared staging/dev clusters; do not point them at production targets.
- Use short-lived cluster credentials. Prefer cloud OIDC / Workload Identity Federation and least-privilege RBAC for the CI service account over long-lived kubeconfig secrets. Never hardcode kubeconfigs, tokens, or registry credentials in workflow files — use the CI platform's secret store.
- Always set a TTL (
ttl_mins/ttl_secs) so an exposed preview environment tears itself down and cannot linger unattended on a shared cluster.
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.
- yesterday First seen · 509 lines · 122 tokens per session scan A a003d0037a46
mirrord-prev-env is a skill published in the GitHub repository metalbear-co/mirrord (5,361 stars, last pushed today), licensed MIT. It adds 122 tokens to every session and 8,596 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-09.
Other skills, from other repositories
scanning-kubernetes-manifests-with-kubesec
Perform security risk analysis on Kubernetes resource manifests using Kubesec to identify misconfigurations, privilege escalation risks, and deviations from security best practices.
chaos-experiment
Design and document chaos engineering experiments. Guide steady state baseline, hypothesis formation, failure injection plans, and results analysis. Use when you say "design a chaos experiment", "plan a game day", "failure injection", "test resilience", or "chaos engineering". Do NOT use for security threat analysis…
huawei-deployment
Use when creating, managing, or running deployment tasks and pipelines on Huawei Cloud CloudDeploy. Triggers: CloudDeploy, deployment, CI/CD, pipeline, release, artifact deployment, deploy task. NOT for: CodeArts Build (build pipeline), SWR container registry.
deploy-verify
Deploy to staging/preview and prove it works before anything reaches users — runs pre-flight gates (types, tests, env, migrations, build), deploys, smoke-tests the live URL, diagnoses failures, and ends by writing a machine-readable verdict artifact that a release orchestrator can trust. Use for "/deploy-verify"…
set-up-abi-compatibility-ci
Set up automated ABI compatibility checking for a C/C++ shared library in a GitHub repository's GitHub Actions CI. Use when asked to add, enable, integrate, or configure ABI checking or a breaking-change gate in GitHub Actions, to onboard a native library project onto continuous compatibility checking, to make pull…
azure-devtest-labs
Expert knowledge for Azure DevTest Labs development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing lab VM images, ARM/CI-CD automation, RBAC/Key Vault security…