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/happenmass/codex-claude-code-mcp/claude-code-blocking-backgroundnpx skills add Happenmass/codex-claude-code-mcp --skill claude-code-blocking-backgroundgit clone --depth 1 https://github.com/Happenmass/codex-claude-code-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/skills/happenmass/codex-claude-code-mcp/claude-code-blocking-background)<a href="https://agentmods.dev/skills/happenmass/codex-claude-code-mcp/claude-code-blocking-background"><img src="https://agentmods.dev/badge/skills/happenmass/codex-claude-code-mcp/claude-code-blocking-background.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.00076 | $0.00637 |
| Opus 5 | $0.00038 | $0.00318 |
| Sonnet 5 | $0.00015 | $0.00127 |
| Haiku 4.5 | $0.00008 | $0.00064 |
Grade A, and why
claude-code-blocking-background 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.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Blocking Background
Use a native Codex subagent as the owner of the blocking MCP call. Do not create a separate user-owned Codex task and do not poll the MCP.
Delegate
- Split out one concrete Claude task that can run independently. Do not delegate work whose result is required before any safe parent work can begin.
- If the user asks which models are available, requests model selection, or supplies an uncertain model identifier, call
claude_code_modelsonce in the parent before spawning. Pass its returnedvalueto the child. Model discovery is short and does not belong in the background subagent. - Spawn one native Codex subagent with a prompt that includes:
- the complete task, working directory, scope, constraints, desired output, and requested Claude model;
- an instruction to call
claude_code_runexactly once throughclaude-code-blocking; - the minimum explicit
allowedTools,askTools, anddisallowedTools; - an instruction not to spawn another agent, not to poll, and to wait for the MCP call to return;
- an instruction to report the result, terminal status, and
sessionIdwithout dropping material details.
- Keep the returned subagent identifier.
- Continue useful independent work in the parent agent. Do not immediately wait unless no independent work remains or the user asked only for the Claude result.
- When the result becomes necessary, use Codex's native agent wait/mailbox primitive. Avoid repeated status narration or application-level polling.
- Integrate the subagent's returned Claude result, clearly attributing it to Claude.
Suggested child instruction:
Call
claude_code_runexactly once through theclaude-code-blockingMCP for the task below. Do not spawn agents or poll. Wait for the blocking call to return, then report its result, status, and session ID.
Resume
To continue the same Claude session in the background, spawn or re-task a native subagent to call claude_code_resume exactly once with the prior sessionId. Keep the parent/child ownership and waiting pattern unchanged.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 39 lines · 76 tokens per session scan A 0d47c4d5b043
claude-code-blocking-background is a skill published in the GitHub repository Happenmass/codex-claude-code-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 637 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…