What is codex-ready-workspace?

A workspace setup tool that creates or updates onboarding guidance for Codex in a repository or project folder. It can prepare files such as AGENTS.md and README.md so the workspace explains how to work in it.

Use it to inspect an existing project, create missing starter guidance, or make an empty workspace ready for Codex without replacing existing files unless asked.

It reduces repeated explanations about the project and helps Codex understand the workspace at the start of each task.

codex-ready-workspace — Skill for Codex by Berkantcen

Install

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.

Any agent

npx skills add Berkantcen/codex-productivity-starter --skill codex-ready-workspace

Clone the repo

git clone --depth 1 https://github.com/Berkantcen/codex-productivity-starter

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/berkantcen/codex-productivity-starter/codex-ready-workspace/github.svg)](https://agentmods.dev/skills/berkantcen/codex-productivity-starter/codex-ready-workspace)

Your own site

<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.

Your own site · 80×15

<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>

Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,132 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00041	$0.00453
Sonnet 5.5	$0.00020	$0.00226
Haiku 4.5	$0.00010	$0.00113

Measured 2mo ago against content hash e85095fdccdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/init_codex_workspace.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/codex-productivity/skills/codex-ready-workspace/SKILL.md · 106 lines

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 --files when available to understand structure.
- Check git status --short --branch when the workspace is a git repository.
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:

Read the full file on GitHub · 106 lines

Files

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.

Changes

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.

2mo ago First seen · 106 lines · 102 tokens per session scan A e85095fdccdb

Subscribe to this mod's changes

codex-ready-workspace is a skill published in the GitHub repository Berkantcen/codex-productivity-starter (10 stars, last pushed 3mo ago), licensed MIT. It adds 102 tokens to every session and 1,132 once invoked, about $0.0004 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-31.

codex-ready-workspace next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
codex-ready-workspaceBerkantcen/codex-productivity-starter	Skill	10	3mo ago	MIT	A	102	Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code