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-naminggit 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-naming)<a href="https://agentmods.dev/skills/patrick-fu/awesome-skills/codex-session-naming"><img src="https://agentmods.dev/badge/skills/patrick-fu/awesome-skills/codex-session-naming.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.00062 | $0.00752 |
| Opus 5 | $0.00031 | $0.00376 |
| Sonnet 5 | $0.00012 | $0.00150 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
codex-session-naming 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Session Naming
A user-visible top-level domain work session owes one mandate. The session title is the headline:
<state> [tags] <mandate> · <gate>
Tags are at most two searchable scope or facet labels. Keep user phrasing,
IDs, and entities. Controller-role titles belong to
codex-session-controller.
When
- Entry: before the first response, write the headline from available
evidence. With no usable mandate, use
🙋 新会话 · 等待目标. - Semantic transition: before the response that ends a turn, rewrite only when the headline is false; if true, leave it. Judge from user intent, delivered or verified work, and actual blockers—not recency or runtime alone.
- Closure: decide
🏁and☑️under Claim.
Mandate
The mandate is the final boundary this session still owes, not the current action or method. An explicit user correction may revise that same boundary. While the current boundary is still owed, new work is evaluated under Gate, not as a new mandate. It ends only when revoked (explicitly released), discharged (final closure passes), or transferred (an accepted successor owns it). After it ends, a new mandate starts only on evidence that this session now owes another final boundary. With no new mandate, the closing headline keeps the old one.
Gate
The gate is the mandate's one bottleneck: the hold or step that first decides whether the mandate can advance. Keep it while it remains the bottleneck; with no hold, use the decisive next step. Activity outside the bottleneck does not enter the headline.
Owner
The owner is who must take the next step through the chosen gate, and selects the state. Completion and handoff override:
🏁mandate discharged☑️checkpoint passed and parked🔀accepted successor owns unfinished work🙋user decision, authorization, or action🕒time, device, review, build, or external system⛔no valid path⏸️user pause⏳owned queue not started🏃Agent-owned active work; its working Agent may use one self-explanatory emoji for its current action. Fall back to🏃; all other states stay fixed.
What ships with it
2 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.
- 3d ago Changed · -2 lines · -3 tokens per session 83d6a189b23a
- 7d ago First seen · 82 lines · 65 tokens per session scan A 7de5d3bfc322
codex-session-naming is a skill published in the GitHub repository patrick-fu/awesome-skills (57 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 752 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…