技能 mirrord-ci

📦

mirrord-ci

Name: mirrord-ci
Author: metalbear-co

v1.4 内容修订 r1 高风险 ⚙️ 外部命令🌐 网络访问📁 文件系统访问🔑 环境变量

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.

支持: Claude Codex Code(CC)

⚠️ 38 差

安装前请停下并请求确认。

请审查安装计划，并在更改文件前获得用户明确同意。

使用我的智能体安装

将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。

智能体请求

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.

你的智能体仍应展示其计划，并按安全策略请求必要确认。

Agent 可读资源

当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。

Markdown 详情 GET /skills/metalbear-co-mirrord-ci.md 已签名 manifest GET /api/skills/metalbear-co-mirrord-ci/manifest 已签名 lockfile GET /api/skills/metalbear-co-mirrord-ci/lockfile

测试它

正在使用“mirrord-ci”。 Plan a GitHub Actions integration test job for our staging API.

预期结果:

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.

正在使用“mirrord-ci”。 Our Next.js application behaves differently when CI connects through mirrord.

预期结果:

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.

正在使用“mirrord-ci”。 Certificate errors appeared after moving tests to a macOS runner.

预期结果:

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.

安全审计

高风险

v1 • 2026/9/29 打开版本化报告

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.

已扫描文件

4,165

分析行数

复核项

已忽略误报

已确认安全问题 (4)

高

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.

高

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.

中

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.

中

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.

能力复核项 (1)

这些是真实的本地能力，对此技能可能是预期行为，因此需要复核，但不会按已确认恶意行为计分。

高

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.

风险因素

⚙️ 外部命令 (50)

🌐 网络访问 (47)

📁 文件系统访问 (30)

🔑 环境变量 (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

审计者: codex

分享与引用此报告

分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。

打开版本化报告

复制报告链接

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

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)

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>

嵌入卡片

<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>

学术引用 (APA · BibTeX · CFF)

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

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"

Skillstore 评分

评分依据证据置信度: 中

架构

可维护性

内容

社区

规范符合性

你能构建什么

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.

试试这些提示

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.

最佳实践

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.

避免

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.

常见问题

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.