📦

mirrord-ci

Name: mirrord-ci
Author: metalbear-co

v1.4 Revisão do conteúdo r1 Risco alto ⚙️ Comandos externos🌐 Acesso à rede📁 Acesso ao sistema de arquivos🔑 Variáveis de ambiente

Configure mirrord CI Tests for Kubernetes

Integration tests often require access to services already running in Kubernetes. This skill guides mirrord CI setup with platform-specific workflows, configuration validation, and session cleanup.

Suporta: Claude Codex Code(CC)

⚠️ 38 Ruim

Pare e solicite confirmação antes de instalar.

Revise o plano e obtenha o consentimento explícito do usuário antes de alterar arquivos.

Instalar com meu Agente

Copie esta solicitação para o seu Agente. Ela inclui a página canônica do Skill e o manifesto.

Solicitação do agente

Review the Skillstore skill "mirrord-ci" from https://skillstore.io/skills/metalbear-co-mirrord-ci.md and its manifest at https://skillstore.io/api/skills/metalbear-co-mirrord-ci/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Seu Agente ainda deve apresentar o plano e solicitar qualquer confirmação exigida pela política de segurança.

Recursos legíveis por agentes

Use estes links quando um agente de IA, crawler ou script precisar de contexto limpo em vez de ler a página completa.

Detalhe em Markdown GET /skills/metalbear-co-mirrord-ci.md manifest assinado GET /api/skills/metalbear-co-mirrord-ci/manifest lockfile assinado GET /api/skills/metalbear-co-mirrord-ci/lockfile

Testar

Usando "mirrord-ci". Plan a GitHub Actions integration test job for our staging API.

Resultado esperado:

Prerequisites: confirm the mirrord version, Operator entitlement, runner connectivity, and dedicated staging credentials.
Workflow: check out the application, configure authentication, start the target session, and run integration tests.
Cleanup: stop the session regardless of test success.
Safety review: confirm test data isolation and prevent untrusted changes from receiving cluster credentials.

Usando "mirrord-ci". Our Next.js application behaves differently when CI connects through mirrord.

Resultado esperado:

Check whether remote environment values conflict with the local Next.js or Nx runtime.
Review NODE_ENV and NX_NEXT_DIR without printing secret values.
Propose targeted environment exclusions and validate the resulting mirrord configuration before another test run.

Usando "mirrord-ci". Certificate errors appeared after moving tests to a macOS runner.

Resultado esperado:

Compare the runner trust store with the container certificate chain.
Configure approved trust roots instead of accepting every certificate.
Treat any temporary certificate bypass as a security exception requiring explicit approval.

Auditoria de segurança

Risco alto

v1 • 29/09/2026 Abrir o relatório versionado

Of 400 supplied alerts, 399 concern documentation or intended CI operations; signature removal presents a genuine integrity risk. Four semantic findings cover certificate bypass, privileged containers, cluster-wide network changes, and unsupported isolation assurances. No evidence found of prompt injection or covert exfiltration; two omitted static matches still require manual review. Static review was capped at 400/402 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

Arquivos analisados

4,165

Linhas analisadas

Itens de revisão

Falsos positivos ignorados

Preocupações de segurança confirmadas (4)

Alto

SKILL.md:367 references/troubleshooting.md:107-119

Troubleshooting Recommends Disabling Certificate Validation

The guidance recommends "trust_any_certificate": true for certificate errors and states that every certificate becomes trusted. This can expose application connections to server impersonation and interception.

The troubleshooting example explicitly enables universal certificate trust without limiting it to an isolated diagnostic session or requiring restoration.

Alto

SKILL.md:365 references/troubleshooting.md:91-101

Permission Troubleshooting Broadens Container Privileges

The instructions recommend "privileged": true for permission or DNS failures. Privileged agents weaken container isolation and can expose the host when compromised.

The advice directly enables privileged execution without requiring administrator approval or evaluating narrower permissions. Actual exposure depends on deployment policy.

Médio

references/troubleshooting.md:49-60

CI Troubleshooting Changes Cluster-Wide Networking

The Cilium workaround upgrades the release in kube-system and restarts its DaemonSet. Applying it without administrator review can disrupt networking for unrelated workloads.

The commands directly change cluster networking infrastructure, but the surrounding instructions provide no change approval, maintenance window, or rollback requirement.

Médio

SKILL.md:51-56 SKILL.md:182-189 references/schema.json:2501

Isolation Assurance Omits Shared Dependency Side Effects

The skill promises isolated execution without workload interference, but its examples connect directly to shared services without configuring database or traffic isolation. Tests can therefore modify shared data or trigger downstream effects.

The unconditional assurance exceeds the protections configured in the examples. The schema documents outbound traffic tunneling, which does not itself isolate dependency writes.

Itens de revisão de capacidade (1)

Estas são capacidades locais reais que podem ser esperadas para esta habilidade, portanto exigem revisão, mas não são contabilizadas como comportamento malicioso confirmado.

Alto

references/troubleshooting.md:15

sudo privilege escalation

`sudo codesign --remove-signature ./<your-binary>`

The command uses sudo to remove a copied binary's signature for SIP troubleshooting. This weakens binary integrity protections despite its legitimate compatibility purpose.

Fatores de risco

⚙️ Comandos externos (50)

🌐 Acesso à rede (47)

📁 Acesso ao sistema de arquivos (30)

🔑 Variáveis de ambiente (11)

references/schema.json:2667 references/schema.json:2722 references/schema.json:1129 SKILL.md:130 SKILL.md:186 SKILL.md:217 SKILL.md:245 SKILL.md:263 SKILL.md:354 SKILL.md:422 SKILL.md:437

Auditado por: codex

Compartilhar e citar este relatório

Compartilhe o relatório de avaliação versionado, o badge neutro, o cartão incorporável e as citações. A Skillstore apresenta evidências sem decidir se este Skill é seguro.

Abrir o relatório versionado

Copiar link do relatório

https://skillstore.io/skills/metalbear-co-mirrord-ci/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/metalbear-co-mirrord-ci/security.svg)](https://skillstore.io/skills/metalbear-co-mirrord-ci?utm_source=security_passport_badge)

Badge HTML

<a href="https://skillstore.io/skills/metalbear-co-mirrord-ci?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/metalbear-co-mirrord-ci/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Cartão incorporável

<iframe src="https://skillstore.io/embed/skills/metalbear-co-mirrord-ci.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citações acadêmicas (APA · BibTeX · CFF)

Citação APA

metalbear-co. (2026). mirrord-ci security audit report (audit version 1) [Author version 1.4]. Skillstore. https://skillstore.io/skills/metalbear-co-mirrord-ci/audits/1

Citação BibTeX

@techreport{metalbear-co-metalbear-co-mirrord-ci-2026,
  author = {metalbear-co},
  title = {mirrord-ci security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/metalbear-co-mirrord-ci/audits/1},
  note = {Author version 1.4}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "mirrord-ci security audit report (audit version 1)"
version: "1.4"
type: report
authors:
  - name: "metalbear-co"
date-released: "2026-09-29"
url: "https://skillstore.io/skills/metalbear-co-mirrord-ci/audits/1"
identifiers:
  - type: other
    value: "skillstore:metalbear-co-mirrord-ci:audit:1"
    description: "Skillstore immutable audit report identifier"

Pontuação do Skillstore

Por que esta pontuação Confiança das evidências: Médio

Arquitetura

Manutenibilidade

Conteúdo

Comunidade

Conformidade com a especificação

O que você pode criar

Add Staging Integration Tests

Create a GitHub Actions workflow that starts an application with mirrord, runs integration tests, and stops sessions after failures.

Standardize CI Cluster Access

Adapt authentication, namespace permissions, secret references, and cleanup hooks for the CI platforms used across a team.

Diagnose Failed Test Sessions

Investigate missing traffic, environment conflicts, linking issues, or log locations before making changes to shared infrastructure.

Teste estes prompts

Check Readiness

Help me prepare mirrord CI for [CI platform]. Ask about my Kubernetes target, CLI version, cluster access, and licensing before suggesting changes.

Create a CI Workflow

Create a [CI platform] workflow for deployment [name] in namespace [namespace]. Use [application command] and [test command], secret references, approved installation, and cleanup after failures.

Investigate a Failed Session

Diagnose this mirrord CI failure using sanitized logs: [logs]. Check target selection, runtime compatibility, environment filters, and port mapping. Ask before changing cluster settings.

Review Shared Cluster Safety

Review [workflow] and [mirrord configuration] for shared staging use. Assess permissions, traffic filters, dependency writes, secret exposure, and cleanup. Validate proposed configuration and require approval for security exceptions.

Boas práticas

Use approved, pinned tooling and restrict cluster credentials to trusted jobs with the minimum required permissions.
Validate mirrord configuration and verify traffic and data isolation before testing against shared services.
Always stop sessions after tests and require explicit approval for privilege, certificate, or cluster networking changes.

Evitar

Giving untrusted pull request code access to shared cluster credentials or Enterprise API keys.
Treating mirrord connectivity as automatic isolation from shared database writes and external side effects.
Copying privileged mode, certificate bypass, or cluster networking workarounds into routine CI without review.

Perguntas frequentes

Which AI tools can use this skill?

The skill supports Claude, Codex, and Claude Code.

Which CI platforms have examples?

The source includes GitHub Actions, GitLab CI, CircleCI, and Jenkins examples.

What must already be available?

The guide requires mirrord CLI 3.181.0 or later, Kubernetes access, kubeconfig, and a licensed Operator. Confirm current entitlement requirements before implementation.

How should CI secrets be handled?

Use your CI secret store for Kubernetes credentials and the Enterprise CI API key. Restrict access to trusted jobs and avoid logging values.

Does mirrord guarantee isolated tests?

No. Configure traffic selection and test data isolation explicitly, because application requests can still affect shared services.

Are all troubleshooting suggestions safe defaults?

No. Certificate bypass, privileged containers, signature removal, and cluster networking changes require security review and explicit approval.