Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Lykhoyda/ask-llm/plugin install 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-resume)<a href="https://agentmods.dev/skills/lykhoyda/ask-llm/codex-pair-resume"><img src="https://agentmods.dev/badge/skills/lykhoyda/ask-llm/codex-pair-resume.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.00051 | $0.00646 |
| Opus 5 | $0.00026 | $0.00323 |
| Sonnet 5 | $0.00010 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
codex-pair-resume 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portable contract
Remove the project-local pause sentinel and clear the consecutive-failure counter so the next successful edit can be reviewed. Missing state is a no-op.
Host adapters
Pi adapter
Run /codex-pair-resume or remove the sentinel and failure counter 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.
Resume codex-pair for this project
Removes the pause sentinel written by /codex-pair-pause, restoring normal codex-pair review behavior. The .codex-pair/context.md marker and .codex-pair/state/ directory are left in place (the directory holds the cache, inflight locks, and any other future state per ADR-092).
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 resume." -
Check whether the pause sentinel exists at
<marker-dir>/.codex-pair/state/paused:- If it does not exist, tell the user: "codex-pair was not paused — no
.codex-pair/state/pausedsentinel found. No change." - If it exists and is non-empty, it is an auto-pause written by the hook itself
(quota exhaustion or repeated failures — see #176).
catit and show the user thekind,reason, andresetHintfields before removing, so they know whether the provider has likely recovered. - Remove it, together with the consecutive-failure counter — resuming while
the counter is still at threshold would re-pause on the very next single
failure. Quote the paths so marker directories with spaces work:
rm -f -- "<marker-dir>/.codex-pair/state/paused" "<marker-dir>/.codex-pair/state/failures.json"
- If it does not exist, tell the user: "codex-pair was not paused — no
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.
- 8d ago First seen · 53 lines · 51 tokens per session scan A 4e880636ca3f
codex-pair-resume is a skill published in the GitHub repository Lykhoyda/ask-llm (17 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 646 once invoked, about $0.0003 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-30.
Other skills, from other repositories
close
Update version tracking when finishing work on a skill bundle. Use when you're done editing a skill project and need to bump version headers, recompute manifest hashes, update the changelog, flag stale files, or prepare a commit message. Triggers on: "close the session", "update versions", "save the bundle", "I'm done…
prs
Expertise in managing the Git and GitHub Pull Request lifecycle, including staging changes, generating PR descriptions, and branch management.
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.
git-commit
Analyze changes with Git only and auto-generate conventional commit messages with optional emoji; suggests splitting commits when needed, runs local Git hooks by default (use --no-verify to skip).
release
Release a new version of the DevoxxGenie IntelliJ plugin — prompt for the target version, bump it in the build files, write a curated CHANGELOG.md entry and plugin.xml change-notes from the git/PR history since the last tag, build to verify, then commit, tag, and publish a matching GitHub release. Use this whenever…
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.