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 Berkantcen/codex-productivity-starter --skill codex-ready-workspacegit clone --depth 1 https://github.com/Berkantcen/codex-productivity-starterWrote 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/berkantcen/codex-productivity-starter/codex-ready-workspace)<a href="https://agentmods.dev/skills/berkantcen/codex-productivity-starter/codex-ready-workspace"><img src="https://agentmods.dev/badge/skills/berkantcen/codex-productivity-starter/codex-ready-workspace/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/berkantcen/codex-productivity-starter/codex-ready-workspace"><img src="https://agentmods.dev/badge/skills/berkantcen/codex-productivity-starter/codex-ready-workspace.svg" alt="Reviewed on agentmods" width="80" 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.00102 | $0.01132 |
| Opus 5 | $0.00051 | $0.00566 |
| Sonnet 5 | $0.00020 | $0.00226 |
| Haiku 4.5 | $0.00010 | $0.00113 |
Grade A, and why
codex-ready-workspace 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 9d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Ready Workspace
Overview
Create concise, practical workspace guidance that helps Codex work with less repeated context. Favor files that non-technical users can ask Codex to create or update with a simple prompt.
Workflow
- Determine the workspace mode:
- Existing workspace: files, folders, README, package/build files, docs, or source are present.
- Empty workspace: no meaningful project files exist yet.
- For an existing workspace, inspect before writing files:
- Read existing
AGENTS.md,README.md, package/build files, docs, and obvious source directories. - Run
rg --fileswhen available to understand structure. - Check
git status --short --branchwhen the workspace is a git repository.
- Read existing
- For an empty workspace, ask the guided intake questions before writing final content.
- Create missing starter files from bundled assets using
scripts/init_codex_workspace.py. - Do not overwrite existing files unless the user explicitly asks for replacement.
- Replace generic placeholders with concrete facts discovered from the workspace or provided in chat.
- Keep the generated guidance short enough to be loaded at task start.
- Report created files, skipped existing files, assumptions, and validation.
Empty Workspace Intake
When there is nothing useful to inspect, ask concise questions in chat before filling the files. Keep the questions non-technical and avoid asking for terminal commands.
Ask these first:
- What is the workspace or project name?
- What kind of work will happen here? Examples: software project, analysis, product planning, operations, documentation, research.
- Who will use this workspace? Examples: developers, analysts, product managers, QA, leadership.
- What should Codex help with most often?
- Are there files, data, systems, or topics Codex should avoid?
- How should Codex prove work is ready? Examples: tests, reviewed document, checked spreadsheet, manual checklist, stakeholder approval.
If the user has a technical project in mind, also ask:
What ships with it
8 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.
- agents/openai.yaml 188 B
- assets/project-starter/AGENTS.md 1.3 KB
- assets/project-starter/decision-log.md 775 B
- assets/project-starter/handoff-summary.md 407 B
- assets/project-starter/repo-map.md 1.4 KB
- assets/project-starter/task-brief.md 1019 B
- assets/project-starter/validation-plan.md 1.2 KB
- scripts/init_codex_workspace.py 2.4 KB runs code
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.
- 9d ago First seen · 106 lines · 102 tokens per session scan A e85095fdccdb
codex-ready-workspace is a skill published in the GitHub repository Berkantcen/codex-productivity-starter (10 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 1,132 once invoked, about $0.0005 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.
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…