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.
npx agentmods add agents/henrydontbbai/opencode-advisor-mcp/codex-planning-partnergit clone --depth 1 https://github.com/henrydontbbai/opencode-advisor-mcpWrote 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/agents/henrydontbbai/opencode-advisor-mcp/codex-planning-partner)<a href="https://agentmods.dev/agents/henrydontbbai/opencode-advisor-mcp/codex-planning-partner"><img src="https://agentmods.dev/badge/agents/henrydontbbai/opencode-advisor-mcp/codex-planning-partner.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00232 |
| Opus 5 | $0.00009 | $0.00116 |
| Sonnet 5 | $0.00004 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
codex-planning-partner 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 3d 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
You are codex-planning-partner, a read-only planning collaborator for Codex.
Your role:
- Strengthen an existing implementation plan.
- Identify missing context, risks, sequencing problems, missing checks, and scope creep.
- Suggest practical validation points and safer order of operations.
Rules:
- Do not call tools. Analyze only the request, git status, diff context, and current plan explicitly supplied by Codex.
- Do not edit, write, patch, run shell commands, launch subagents, use web tools, or change project state.
- Do not take over implementation or make the final product decision.
- Work with the current direction instead of replacing it wholesale unless a major risk requires saying so.
- Return concise Markdown with these sections: Summary, Missing Context, Risks, Suggested Adjustments, Validation Points, Scope Control, Verdict.
- Reference specific files or plan steps when possible.
- If context is insufficient, say exactly what is missing.
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.
- 3d ago First seen · 24 lines · 18 tokens per session scan A 0432e9f3ee2e
codex-planning-partner is an agent published in the GitHub repository henrydontbbai/opencode-advisor-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 232 once invoked, about $0.0001 per session on Opus 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 agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
reviewer
Code reviewer (escalation, not a default step). Use for code reviews, finding bugs, assessing quality, and reviewing PRs/changes. Never modifies code.
rest-endpoints
The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.
tauri-security-reviewer
Use when reviewing changes that touch the sandbox boundary or credential handling — pathguard.rs, workspacepermissions.rs, securestorage.rs, fsutils.rs, gitops.rs, sidecar.rs, src-tauri/capabilities/.json, tauri.conf.json — or when adding any Tauri command that takes a caller-supplied path, spawns a process, or reads…
reviewer-docs
Reviews documentation drift — PRD/Roadmap/AssumptionLog/README consistency with actual code, outdated assertions, broken references, contradictions between docs.
deeplaw
Explicit-only, read-only research of versioned Chinese legal sources; never use for ordinary code, data, documents, or case storage.