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/zebbern/agent-collabWrote 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/plugins/zebbern/agent-collab/codex)<a href="https://agentmods.dev/plugins/zebbern/agent-collab/codex"><img src="https://agentmods.dev/badge/plugins/zebbern/agent-collab/codex/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/plugins/zebbern/agent-collab/codex"><img src="https://agentmods.dev/badge/plugins/zebbern/agent-collab/codex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
codex 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 1mo 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.
What it actually says
{
"name": "codex",
"version": "1.0.6+fork.9",
"description": "Use Codex from Claude Code to review code or delegate tasks. Community fork by zebbern.",
"author": {
"name": "zebbern"
}
}
What it installs
The manifest is a name and a version. 4 skills, 11 commands, 1 agent, 3 hooks travel with it, and installing the plugin installs all of them — 351 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill codex-delegation A 74 tokens
- Skill codex-cli-runtime A 19 tokens
- Skill gpt-5-4-prompting A 40 tokens
- Skill codex-result-handling A 18 tokens
- Command doctor A 13 tokens
- Command status A 16 tokens
- Command task A 17 tokens
- Command help A 13 tokens
- Command rescue A 20 tokens
- Command adversarial-review A 13 tokens
- Command review A 10 tokens
- Command setup A 17 tokens
- Command result A 14 tokens
- Command transfer A 13 tokens
- Command cancel A 10 tokens
- Agent codex-rescue A 44 tokens
- Hook Stop A not measured
- Hook SessionStart A not measured
- Hook SessionEnd A not measured
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.
- 1mo ago First seen · 9 lines scan A bd7ea4a67b83
codex is a plugin published in the GitHub repository zebbern/agent-collab (34 stars, last pushed 16d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-30.
Other plugins, from other repositories
uniclaude
Unity development skills for UniClaude — architecture decisions, MCP tool workflows, and code review.
code-refactoring
Code cleanup, refactoring automation, and technical debt management with context restoration.
comprehensive-review
Multi-perspective code analysis covering architecture, security, and best practices.
jury
Jury v0.1.0 — standalone cross-family cascade-then-jury reviewer (Gemini + GPT small-fish → cross-family tiebreaker). The free 'jury beats judge' base; codi and super-developer depend on it optionally for cross-family verification. No API keys (OAuth local CLIs).
dev-pipeline
A 5-phase development pipeline (requirement engineering, system architecture, task generation, verified implementation, code review) with an optional QA gate (plan-qa + execute-qa) for changes that have a running surface worth driving — independent of /review, run sequentially or in parallel at the developer's…
architecture-reviewer
Audit code against architecture documentation — detects drift between design and implementation.