ccc-e2e SKILL.md skillA
ccc-e2e from kevinzai/commander is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kevinzai/commander/ccc-e2e@git:20261013.fbe187dPins git:20261013.fbe187d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kevinzai/commander
- Path
commander/cowork-plugin-codex/skills/ccc-e2e/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261013.fbe187d, committed Oct 13, 2026
- First version recorded
- May 1, 2026
- Size
- 8,583 bytes
- Repository stars
- 6
- License
- MIT
Pre-release assessment that fans out via $ccc-fleet into up to three isolated workers (QA audit, unit tests, Playwright E2E) running $ccc-testing lanes, then writes a severity-ranked PASS or FAIL verdict. Use when about to tag a release, after a large merge, or asking is this ready.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# $ccc-e2e — Full-surface confidence before shipping
**CC Commander** · $ccc-e2e · parallel QA, unit and E2E workers, one honest verdict
Composes `$ccc-fleet` (parallel dispatch, worktree isolation) with `$ccc-testing` (testing lanes). Audit only: workers find and report, they do not fix.
## When to use / when not to
- Use before tagging a major or minor release, after merging a feature that touches five or more files, after a cross-module refactor, or when the user feels coverage is thin but cannot say where.
- Quick bug-fix patch: `$ccc-review`. Single-file change: `$ccc-testing`. Docs-only change: skip. Hotfix under time pressure: `$ccc-ship` pre-flight.
- Codex: ask pickers as plain-text questions and run each worker as `codex exec --json --sandbox workspace-write` in its own `git worktree`; the session tools below are skipped.
## What happens
### 1. Context strip
Run in parallel, silent on failure:
```bash
git rev-parse --abbrev-ref HEAD
BASE=$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's#^origin/##'); BASE=${BASE:-main}
git rev-list --count "$BASE"..HEAD 2>/dev/null
git diff --shortstat "$BASE"..HEAD 2>/dev/null
…Read the whole file at its exact version.
How to install
mdr add kevinzai/commander/ccc-e2e@sha256:88e5ccc6f0bf32dcThe line at the top of this page pins the label git:20261013.fbe187d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_t6xcsep6ypt4eib7)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 1, 2026 and Oct 13, 2026, about one every 41 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261013.fbe187d latest | 2026-10-13 | fbe187d | 8,583 B | A | view · diff |
| git:20260722.9d3ab82 | 2026-07-22 | 9d3ab82 | 9,441 B | A | view · diff |
| git:20260707.947ab2f | 2026-07-07 | 947ab2f | 9,309 B | A | view · diff |
| git:20260514.2648602 | 2026-05-14 | 2648602 | 9,140 B | A | view · diff |
| git:20260501.27abf7b | 2026-05-01 | 27abf7b | 9,156 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8583 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kevinzai/commander · 6 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t6xcsep6ypt4eib7 GET https://markdownregistry.com/api/v1/resolve?ref=kevinzai/commander/ccc-e2e GET https://markdownregistry.com/api/v1/blob/88e5ccc6f0bf32dcb9035799fef26a5b89b8f117f5bf5c016996e03497caba88
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kevinzai/commander
Every file in kevinzai/commander