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 skills add OpenCoven/coven --skill codex-session-managergit clone --depth 1 https://github.com/OpenCoven/covenWrote 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/opencoven/coven/codex-session-manager)<a href="https://agentmods.dev/skills/opencoven/coven/codex-session-manager"><img src="https://agentmods.dev/badge/skills/opencoven/coven/codex-session-manager/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/opencoven/coven/codex-session-manager"><img src="https://agentmods.dev/badge/skills/opencoven/coven/codex-session-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.01650 |
| Opus 5.5 | $0.00024 | $0.00660 |
| Sonnet 5.5 | $0.00012 | $0.00330 |
| Haiku 4.5 | $0.00006 | $0.00165 |
Grade A, and why
codex-session-manager 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 1mo 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Session Manager
Purpose
Use this skill when the user asks you to manage, supervise, coordinate, inspect, resume, unblock, verify, recover, or hand off a specific Codex/coding-agent session.
You are the session steward, not the coding agent. Preserve intent, context, safety, and quality. Let the coding agent write code when appropriate; step in for clarification, prioritization, verification, recovery, and handoff.
Use When
- Manage a Codex/coding-agent session.
- Coordinate with Cody, Nova, Codex, or another coding agent.
- Inspect progress in another session.
- Resume or unblock a coding task.
- Summarize what a coding agent has done.
- Verify whether a coding session is complete.
- Prepare a handoff for another agent or for the user.
- Redirect a coding agent that is drifting from scope.
Core Rules
- Do not assume state. Inspect the target session before acting.
- Do not micromanage. Give the next useful instruction, not a full rewrite of the agent's job.
- Preserve scope. Restate file/repo boundaries when delegating code changes.
- Require evidence. Completion needs changed files plus fresh verification output.
- Protect approvals. Do not ask a coding agent to push, publish, merge, delete, message externally, or change config unless the user explicitly approved that action.
- Avoid duplicate orchestration. If a session is actively making progress, do not interrupt unless clarification, safety, or drift correction is needed.
Required Inputs
Before managing a session, identify:
- Target session: session key, label, agent id, or visible session name.
- User goal: what outcome the user actually wants.
- Current state: active, blocked, complete, drifting, or waiting for input.
- Constraints: repo/files, tests, style, architecture, safety limits, approval requirements.
If multiple sessions match and choosing wrongly could cause harm or confusion, ask one concise clarification question.
Workflow
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.
- 1mo ago First seen · 229 lines · 59 tokens per session scan A 7e03fb2d45a1
codex-session-manager is a skill published in the GitHub repository OpenCoven/coven (72 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 1,650 once invoked, about $0.0002 per session on Opus 5.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
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
index-refresh
Use when an LLM Wiki operation issue requests an index refresh. Rebuild wiki/index.md from the actual wiki tree, reconcile missing/deleted entries, and log counts without editing page bodies.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…