Install the "mirrord-ci" agent skill from https://github.com/metalbear-co/mirrord/tree/main/mirrord/mcp/corpus/skills/mirrord-ci into .claude/skills/mirrord-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirrord-ci", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add metalbear-co/mirrord --skill mirrord-ci -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "mirrord-ci" agent skill from https://github.com/metalbear-co/mirrord/tree/main/mirrord/mcp/corpus/skills/mirrord-ci into .agents/skills/mirrord-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirrord-ci", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add metalbear-co/mirrord --skill mirrord-ci -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "mirrord-ci" agent skill from https://github.com/metalbear-co/mirrord/tree/main/mirrord/mcp/corpus/skills/mirrord-ci into .cursor/skills/mirrord-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirrord-ci", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add metalbear-co/mirrord --skill mirrord-ci -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "mirrord-ci" agent skill from https://github.com/metalbear-co/mirrord/tree/main/mirrord/mcp/corpus/skills/mirrord-ci into .gemini/skills/mirrord-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirrord-ci", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add metalbear-co/mirrord --skill mirrord-ci -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "mirrord-ci" agent skill from https://github.com/metalbear-co/mirrord/tree/main/mirrord/mcp/corpus/skills/mirrord-ci into .github/skills/mirrord-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirrord-ci", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add metalbear-co/mirrord --skill mirrord-ci -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "mirrord-ci" agent skill from https://github.com/metalbear-co/mirrord/tree/main/mirrord/mcp/corpus/skills/mirrord-ci into .opencode/skills/mirrord-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirrord-ci", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
mirrord-ci
GitHub stars
5.4k
Used in
1 other repo
Token cost
~3.2k tokens
SKILL.md length
896 words
Files
3 (incl. references)
Repo updated
First seen
Licence
MIT
At a glance
Help users set up mirrord in CI pipelines for testing against real Kubernetes environments.
Works in 2 steps: Service Account (Recommended) → Cloud Provider Authentication
Users want to run end-to-end tests
SKILL.md covers Purpose, When to Use This Skill, Security note for CI examples and Critical First Steps, plus 8 more sections
Calls kubectl, npm and go; reaches mirrord.dev; needs MIRRORD_CI_API_KEY
What it does
Mirrord CI is an agent skill from metalbear-co/mirrord. Help users set up mirrord in CI pipelines for testing against real Kubernetes environments. Use when users want to run end-to-end tests, integration tests, or automated tests in CI using mirrord to connect to staging/shared clusters.
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `README.md` and `references/troubleshooting.md`).
It sits in DevOps & Cloud, covering CI/CD, Container orchestration and Integration testing. It works with Kubernetes, GitHub Actions and GitLab. The repository describes itself as: Run any process, on your machine or in an AI agent's environment, as if it were a pod in your Kubernetes cluster: real env vars, DNS, network, traffic. The licence is MIT.
When your agent uses it
Users want to run end-to-end tests
Integration tests
Automated tests in CI using mirrord to connect to staging/shared clusters
Example prompts
“/mirrord-ci”
Requirements
Python 3
Node.js
Docker
A credential in MIRRORD_CI_API_KEY
Workflow steps
2 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c8f017a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
kubectl
npm
go
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
mirrord.dev
Also links to:
metalbear.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
MIRRORD_CI_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Mirrord CI loads about 3.2k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 61 tokens; SKILL.md has 896 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~61
When it runs· the whole SKILL.md, loaded when a task matches
~3.2k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~5.6k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: warnings
The automated check found patterns that need a careful read before installing.
WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:174
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/mirrord-ci/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
mirrord-ci
description
Help users set up mirrord in CI pipelines for testing against real Kubernetes environments. Use when users want to run end-to-end tests, integration tests, or automated tests in CI using mirrord to connect to staging/shared clusters.
metadata.author
MetalBear
metadata.version
1.4
Mirrord CI Skill
Purpose
Help users integrate mirrord into CI pipelines for testing against real Kubernetes environments:
Configure CI runners to connect to Kubernetes clusters
Set upmirrord ci start/stop commands in CI workflows
Generate CI workflow files for GitHub Actions, GitLab CI, etc.
Troubleshoot CI-specific mirrord issues
When to Use This Skill
Trigger on questions like:
"How do I use mirrord in CI?"
"Set up mirrord for GitHub Actions"
"Run tests against staging in CI"
"mirrord ci start not working"
"Configure mirrord for GitLab CI"
Security note for CI examples
Do not use remote pipe-to-shell installs or other unverified script execution in CI to install mirrord.
Pre-install mirrord in a trusted CI image, use your org’s approved package manager with pinned versions, or follow official install docs. The YAML below assumes mirrord is already available on the runner unless you add an approved install step.
Critical First Steps
Step 1: Load references
Read the reference files from this skill's references/ directory:
references/troubleshooting.md - Common issues and solutions
The schema defines all valid configuration options for mirrord, including CI-specific settings.
The troubleshooting guide helps diagnose and fix common mirrord issues.
If using absolute paths, search for them using patterns like **/mirrord-ci/references/*.
Step 2: Validate configs before presenting
When generating mirrord configuration files for CI, ALWAYS validate against the schema:
bash
mirrord verify-config /path/to/config.json
Key Benefits of mirrord for CI
Speed: ~50% faster CI pipelines by eliminating test environment setup
Cost: No need to spin up ephemeral clusters for each CI run
Accuracy: Test against real services, dependencies, and configurations
Isolation: Safe, isolated test execution that doesn't interfere with other workloads
Prerequisites
Required
mirrord CLI version 3.181.0 or later
Kubernetes cluster access from the CI runner
kubeconfig configured in CI environment
mirrord Operator installed with a Teams/Enterprise license. No license yet? An AI agent can offer the user a seven-day Enterprise trial and start it once they agree: see the mirrord-operator skill, "Agent-started trial".
Verification commands
bash
# Check mirrord version
mirrord --version
# Verify cluster access
kubectl cluster-info
kubectl get pods -n <target-namespace>
Core Commands
Starting a CI session
bash
mirrord ci start --target <target> -- <your-command>
This starts your application with mirrord in the background, allowing tests to run against it.
Examples:
bash
# Node.js application
mirrord ci start --target deployment/api-server -- npm run start
# Python application
mirrord ci start --target pod/backend-abc123 -- python main.py
# With config file
mirrord ci start --config-file mirrord.json -- ./my-app
# Run in foreground (blocks until stopped)
mirrord ci start --foreground --target deployment/api -- npm start
Stopping CI sessions
bash
mirrord ci stop
This stops all running mirrord CI sessions. Always run this after tests complete.
Multiple sessions
You can start multiple mirrord sessions in a single CI job:
bash
mirrord ci start --target deployment/service-a -- ./service-a &
mirrord ci start --target deployment/service-b -- ./service-b &
# Run tests
npm test
# Stop all sessions
mirrord ci stop
CI API Key (for mirrord Enterprise)
This only applies to the Enterprise plan; if you're on the open-source version of mirrord, skip this section. When the mirrord Operator is installed in the cluster, mirrord ci commands require a CI API key, and generating one requires an Enterprise plan. Without it, every CI runner registers as a new user and consumes a seat:
bash
# Generate the key (run locally, not in CI)
mirrord ci api-key
Store this as a secret environment variable named MIRRORD_CI_API_KEY in your CI platform.
By default, application stdout/stderr are saved to:
/tmp/mirrord/<binary-name>-<unique-id>/
CI Platform Examples
GitHub Actions
yaml
name: Integration Tests
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Set up kubeconfig
run: |
mkdir -p ~/.kube
echo "${{ secrets.KUBECONFIG }}" | base64 -d > ~/.kube/config
- name: Ensure mirrord is installed
run: |
# Use a pre-built runner image that includes mirrord, or install via your org's approved method.
# See https://mirrord.dev/docs/overview/quick-start/ — do not pipe remote install scripts.
mirrord --version
- name: Start app with mirrord
run: |
mirrord ci start --target deployment/api-server -- npm run start
env:
MIRRORD_CI_API_KEY: ${{ secrets.MIRRORD_CI_API_KEY }}
- name: Run tests
run: npm test
- name: Stop mirrord
if: always()
run: mirrord ci stop
GitLab CI
yaml
integration-tests:
stage: test
image: node:20
before_script:
- |
# Install mirrord - use your organization's approved installation method
# See https://mirrord.dev/docs/overview/quick-start/ for options
# Option A: Pre-install mirrord in your CI Docker image
# Option B: Use a pinned version from GitHub Releases with checksum verification
mirrord --version # Verify mirrord is available
- mkdir -p ~/.kube
- echo "$KUBECONFIG_CONTENT" | base64 -d > ~/.kube/config
script:
- mirrord ci start --target deployment/api-server -- npm run start
- npm test
after_script:
- mirrord ci stop
variables:
MIRRORD_CI_API_KEY: $MIRRORD_CI_API_KEY
CircleCI
yaml
version: 2.1
jobs:
integration-test:
docker:
- image: cimg/node:20.0
steps:
- checkout
- run:
name: Setup kubeconfig
command: |
mkdir -p ~/.kube
echo "$KUBECONFIG_B64" | base64 -d > ~/.kube/config
- run:
name: Ensure mirrord is installed
command: |
# Pre-install mirrord in the image or use an org-approved install path (see mirrord docs).
mirrord --version
- run:
name: Start mirrord CI session
command: mirrord ci start --target deployment/api -- npm start
environment:
MIRRORD_CI_API_KEY: ${MIRRORD_CI_API_KEY}
- run:
name: Run tests
command: npm test
- run:
name: Stop mirrord
command: mirrord ci stop
when: always
Jenkins Pipeline
groovy
pipeline {
agent any
environment {
KUBECONFIG = credentials('kubeconfig-staging')
MIRRORD_CI_API_KEY = credentials('mirrord-ci-api-key')
}
stages {
stage('Setup') {
steps {
sh '''
# Ensure mirrord exists on the agent (pre-installed image or org-approved install)
mirrord --version
'''
}
}
stage('Test') {
steps {
sh 'mirrord ci start --target deployment/api -- npm start'
sh 'npm test'
}
post {
always {
sh 'mirrord ci stop'
}
}
}
}
}
Kubernetes Access Setup
The CI runner must have access to your Kubernetes cluster. Common approaches:
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in metalbear-co/mirrord, which our catalogue first saw on October 11, 2026.
Mirrord CI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Rules for designing CI/CD pipelines in layers: universal lint, test and scan stages, container builds with SBOM attestation, and GitOps for orchestrated deployments.
Releases and CI for eserstack: the shared version of all packages, the release command, the tag-driven build.yml run, JSR and npm publishing, changelog and breaking changes, release recovery, GitHub…
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI.
Help users set up mirrord in CI pipelines for testing against real Kubernetes environments. Mirrord CI is an agent skill from metalbear-co/mirrord. Help users set up mirrord in CI pipelines for testing against real Kubernetes environments.
When should I use Mirrord CI?
Mirrord CI fits situations like: users want to run end-to-end tests; integration tests; automated tests in CI using mirrord to connect to staging/shared clusters.
How do I install Mirrord CI in Claude Code?
Run `npx skills add metalbear-co/mirrord --skill mirrord-ci -a claude-code`. Or copy the skill folder (mirrord/mcp/corpus/skills/mirrord-ci in metalbear-co/mirrord) into .claude/skills/mirrord-ci in your project. Claude Code loads it when a task matches its description.
How do I install Mirrord CI in Codex?
Run `npx skills add metalbear-co/mirrord --skill mirrord-ci -a codex`. Or copy the skill folder (mirrord/mcp/corpus/skills/mirrord-ci in metalbear-co/mirrord) into .agents/skills/mirrord-ci in your project. Codex loads it when a task matches its description.
Can I use Mirrord CI in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add metalbear-co/mirrord --skill mirrord-ci -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mirrord-ci, .gemini/skills/mirrord-ci, .github/skills/mirrord-ci and .opencode/skills/mirrord-ci in your project.
What does Mirrord CI need to run?
Going by SKILL.md and its folder, Mirrord CI needs the command-line tools its instructions call (kubectl, npm and go) and credentials named MIRRORD_CI_API_KEY. Our summary lists: Python 3; Node.js; Docker; A credential in MIRRORD_CI_API_KEY.
Does Mirrord CI access the network?
SKILL.md names 2 domains. In commands or code: mirrord.dev; the agent is likely to contact it when it follows the instructions. As links in the text: metalbear.com. This is read from the text; nothing was executed.
Is Mirrord CI safe to install?
Our automated static check of SKILL.md flagged 3 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.
What licence does Mirrord CI use?
Mirrord CI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Mirrord CI use?
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.4k tokens, read only when the agent opens those files.
What are the alternatives to Mirrord CI?
Skills that share tags, products or a category with Mirrord CI: Infrastructure Devops Devops Engineer (chendongqi/OPB-Skills, 126 stars), CI CD (EliasOulkadi/shokunin, 114 stars), Data Processing (aiskillstore/marketplace, 433 stars) and Eks Recon (aws-samples/appmod-blueprints, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mirrord CI?
metalbear-co (a GitHub organization) maintains it in metalbear-co/mirrord, which has 5,362 GitHub stars. The repository was last updated on October 11, 2026.
Source: metalbear-co/mirrord on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.