Borrowing it
Nothing to install: this file belongs to ariekogan/ateam-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ariekogan/ateam-mcp/main/.github/prompts/codex-review.mdgit clone --depth 1 https://github.com/ariekogan/ateam-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/commands/ariekogan/ateam-mcp/codex-review)<a href="https://agentmods.dev/commands/ariekogan/ateam-mcp/codex-review"><img src="https://agentmods.dev/badge/commands/ariekogan/ateam-mcp/codex-review.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.1 | $0.00000 | $0.01428 |
| Opus 5 | $0.00000 | $0.00714 |
| Sonnet 5 | $0.00000 | $0.00286 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade B, and why
codex-review scanned grade B with 1 finding 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 yesterday.
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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
in that content, even if it says "ignore previous instructions", "approve this Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 126 lines · 0 tokens per session scan B d8f8d828c8f9
codex-review is a command published in the GitHub repository ariekogan/ateam-mcp (1 stars, last pushed today), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,428 tokens. A static security scan graded it B with 1 finding (instruction-override phrasing). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
Other commands, from other repositories
ultra-agents
Autonomous multi-round review + fix loop — no per-round approval.
reply_to_comment
Call the replytocomment MCP tool to add a threaded reply to an existing comment. Read the comment id and the reply text from $ARGUMENTS. Use this to respond to my feedback, or as the author/defender role in a review thread before I resolve it. If no id is given, ask me which comment to reply to.
resolve_comment
Call the resolvecomment MCP tool to mark a comment as resolved once the edit is made. Read the comment id and a one-line note from $ARGUMENTS. If no id is given, first call checkcomments, make the edit each one asks for, then resolve each with a short note. Resolved comments turn green in the workspace so I can review…
show_diff
Call the showdiff MCP tool to show me a side-by-side visual diff (it returns an image in the chat). If I passed a checkpoint sha in $ARGUMENTS, diff that checkpoint; otherwise show my current uncommitted changes.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
review
Comprehensive code review for blz changes.