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/opencoven/coven/codex-session-managernpx skills add OpenCoven/coven --skill codex-session-managergit clone --depth 1 https://github.com/OpenCoven/covenWhat 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.00059 | $0.01650 |
| Opus 5 | $0.00030 | $0.00825 |
| Sonnet 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 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 — 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.
- 3d 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 (41 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 1,650 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
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
security-review
Review trust boundaries, auth/authz, injection, secrets, filesystem/network exposure, dependencies, and exploitability without pretending a shallow lint is an audit.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
ui-design-contract
Use this skill before rendering when the direction must persist across multiple screens/components, brand or system work, conflicting references, formal handoff, or a genuinely vague visual system. Ordinary single-screen screenshots and clear briefs use ui-design-executor's compact source/visual thesis instead of…