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 skills/lykhoyda/ask-llm/codex-pair-pausenpx skills add Lykhoyda/ask-llm --skill codex-pair-pausegit clone --depth 1 https://github.com/Lykhoyda/ask-llmWrote 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/skills/lykhoyda/ask-llm/codex-pair-pause)<a href="https://agentmods.dev/skills/lykhoyda/ask-llm/codex-pair-pause"><img src="https://agentmods.dev/badge/skills/lykhoyda/ask-llm/codex-pair-pause.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.00056 | $0.00696 |
| Opus 5 | $0.00028 | $0.00348 |
| Sonnet 5 | $0.00011 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade C, and why
codex-pair-pause scanned grade C 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
For permanent disable, remove the `.codex-pair/` directory instead (`rm -rf .codex-pair/`). For per-file/per-directory opt-out, use `.codex-pair/ignore` (gitignore-style globs). How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portable contract
Create the project-local .codex-pair/state/paused sentinel without removing the marker or history. This is a manual pause and remains until explicitly resumed.
Host adapters
Pi adapter
Run /codex-pair-pause or create the sentinel exactly as described by the portable contract.
Claude Code adapter
The existing detailed workflow below is the Claude Code adapter. Its Agent, MCP, hook, CLAUDE_PLUGIN_ROOT, and AskUserQuestion mechanics apply only on Claude Code; they do not override the Pi adapter above.
Pause codex-pair for this project
Pauses the codex-pair hook for the current project without removing the .codex-pair/context.md marker. The marker (and its project context) stays in place — only the temporary pause sentinel is written. Resume with /codex-pair-resume.
The hook may also pause itself automatically — on provider quota exhaustion or after
3 consecutive review failures — writing the same sentinel with a JSON body that
records why (kind, reason, resetHint). Manual and automatic pauses are resumed
the same way.
When to use
- Starting a noisy refactor where every edit would surface concerns you've already decided to accept
- Working on docs/comments/typos where review adds no value
- Dogfooding the hook itself (avoid recursive self-reviews)
- Burning down a known-issues list where you don't want codex re-flagging them on every save
For permanent disable, remove the .codex-pair/ directory instead (rm -rf .codex-pair/). For per-file/per-directory opt-out, use .codex-pair/ignore (gitignore-style globs).
Instructions
- Locate the
.codex-pair/context.mdmarker by walking up from the current working directory (the project ROOT is the directory holding.codex-pair/). If no marker is found, inform the user: "codex-pair is not enabled in this project (no.codex-pair/context.mdmarker found). Nothing to pause."
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.
- 4d ago First seen · 63 lines · 56 tokens per session scan C 5fb18a57c08b
codex-pair-pause is a skill published in the GitHub repository Lykhoyda/ask-llm (16 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 696 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
glossary-init
USE WHEN setting up a repo for AI-first work, when an agent hallucinates domain term meaning, or when user asks to bootstrap / extend the repo's domain glossary. Surfaces candidate terms by identifier frequency, asks the user for 1-sentence definitions, writes GLOSSARY.md at repo root. Idempotent — re-running adds new…
conventions-init
USE WHEN setting up a repo for AI-first work (after /init-repo), or when the context-surface hook should start feeding repo conventions to agents before edits. Drafts conventions.yml at repo root: per-kind casing (inferred from the code), a vague-name denylist seed, directory roles, and a hand-filled house-rules…
opik
This skill should be used when the user needs to add Opik tracing or integrations to their code, instrument an LLM application, or needs reference for Opik SDK usage (Python, TypeScript, REST API). Use for tasks like "add tracing", "instrument my code", "use trackopenai", "add OpikTracer", "what span types are…
claude-rescue
Use when running under Codex CLI and stuck, wanting a second implementation or diagnosis pass, or handing a substantial task to Claude Code through a real Claude Code subprocess — a genuinely different reasoning system, not another Codex run. Not relevant outside Codex sessions.
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
swarm
Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…