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.
git clone --depth 1 https://github.com/wenqingyu/magic-cc-codex-workerWrote 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/commands/wenqingyu/magic-cc-codex-worker/merge)<a href="https://agentmods.dev/commands/wenqingyu/magic-cc-codex-worker/merge"><img src="https://agentmods.dev/badge/commands/wenqingyu/magic-cc-codex-worker/merge/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/commands/wenqingyu/magic-cc-codex-worker/merge"><img src="https://agentmods.dev/badge/commands/wenqingyu/magic-cc-codex-worker/merge.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.00014 | $0.00126 |
| Opus 5.5 | $0.00006 | $0.00050 |
| Sonnet 5.5 | $0.00003 | $0.00025 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
merge scanned grade A with 0 findings 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 2mo ago.
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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 2mo ago First seen · 12 lines · 14 tokens per session scan A b9dbebb64dd6
merge is a command published in the GitHub repository wenqingyu/magic-cc-codex-worker (5 stars, last pushed 6mo ago), with no licence file. It adds 14 tokens to every session and 126 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
address
Answer reviewer comments on YOUR open PR — categorize unresolved threads, push fixes, and post replies. Workspace-aware across linked PRs.
release
Cut a semver release for the current repo — bump computed from conventional commits, evidence preview, tag + GitHub release.
start
Start a feature — set up an isolated worktree, draft the plan, and write the first failing test before any production code. --jira links a ticket and informs the branch name. Workspace-aware.
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
ccc-fork
Fork the current work into isolated git worktrees to try several approaches side by side, compare them on measured results, and merge the winner. Use when choosing between implementations, attempting a risky refactor, or testing competing bug theories.
ccc-multi-repo
Coordinate one change across several repositories in a single session with --add-dir: shared branch names, linked PRs, dependency-ordered merges and per-repo verification. Use for API contract changes, shared library updates and cross-service refactors.