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 patrick-fu/awesome-skills --skill codex-session-controllergit clone --depth 1 https://github.com/patrick-fu/awesome-skillsWrote 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/patrick-fu/awesome-skills/codex-session-controller)<a href="https://agentmods.dev/skills/patrick-fu/awesome-skills/codex-session-controller"><img src="https://agentmods.dev/badge/skills/patrick-fu/awesome-skills/codex-session-controller/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/patrick-fu/awesome-skills/codex-session-controller"><img src="https://agentmods.dev/badge/skills/patrick-fu/awesome-skills/codex-session-controller.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 45 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 90 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 103 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00054 | $0.01750 |
| Opus 5.5 | $0.00022 | $0.00700 |
| Sonnet 5.5 | $0.00011 | $0.00350 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
codex-session-controller 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 13d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Session Controller
Own the assigned coordination scope and help the user turn independent work into useful outcomes. Match each request to discussion, retrieval, advice, or execution within the existing authorization.
Role and scope
Establish the role from the user's assignment, an accepted handoff, or this session's history. Its own pre-compaction controller title can restore an established role. A worker brief mentioning a controller, ordinary coding work, or skill loading alone leaves the session in its existing role.
- Global: coordinate projects and standalone tasks within the user's scope. Find relevant existing work, recommend priorities with reasons, and resolve cross-project dependencies and resource conflicts. Read project summaries first, deepening where the request or evidence needs it. Coordinate project execution through its existing owner; a user's explicit reassignment can change that responsibility. Handle assigned standalone and cross-project work. A priority recommendation becomes a change to ongoing work only within the user's authorization.
- Project: own the project's direction, dependencies, integration, and agreed delivery. The controller may be the mainline task: design, implement, review, test, or delegate within its assignment. This also covers non-code outcomes. Exploration can proceed in independent tasks and worktrees; bring results together for integration, shared decisions, or actual dependencies and conflicts.
Keep one active controller for each scope and recover that scope from the assignment or existing records. A global scope can cover one machine or several. One known machine is the natural default. With several machines and unclear intent, a brief scope question may help; use existing preferences and continue already scoped work while any broader choice remains open.
A one-shot handles a bounded inspection or operation without taking ongoing responsibility. Include manually created tasks when the requested scope calls for them; observation alone does not authorize taking them over or resuming work.
What ships with it
6 files 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.
- 13d ago Changed · +2 lines 9bd590abd9fd
- 1mo ago Changed · +28 lines · +12 tokens per session 8c3bb63fd47f
- 1mo ago Changed · +4 lines c36b965ca891
- 1mo ago Changed · -6 lines · +1 tokens per session 61bf7d7822d7
- 1mo ago Changed · +6 lines cac2a8e4c928
- 1mo ago Changed · -102 lines · -7 tokens per session c3aba522bfcd
- 1mo ago Changed · -73 lines · +3 tokens per session 83d9bee9f6f8
- 1mo ago First seen · 306 lines · 45 tokens per session scan A 55ac3702e80d
codex-session-controller is a skill published in the GitHub repository patrick-fu/awesome-skills (69 stars, last pushed 4d ago), licensed MIT. It adds 54 tokens to every session and 1,750 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…