Borrowing it
Nothing to install: this file belongs to YankielDBC2/codex-skills-library. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/YankielDBC2/codex-skills-library/main/.agents/skills/codex-progress-journal/SKILL.mdgit clone --depth 1 https://github.com/YankielDBC2/codex-skills-libraryWrote 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/yankieldbc2/codex-skills-library/codex-progress-journal)<a href="https://agentmods.dev/skills/yankieldbc2/codex-skills-library/codex-progress-journal"><img src="https://agentmods.dev/badge/skills/yankieldbc2/codex-skills-library/codex-progress-journal/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/yankieldbc2/codex-skills-library/codex-progress-journal"><img src="https://agentmods.dev/badge/skills/yankieldbc2/codex-skills-library/codex-progress-journal.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.00031 | $0.00303 |
| Opus 5.5 | $0.00012 | $0.00121 |
| Sonnet 5.5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
codex-progress-journal 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.
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.
What it actually says
Codex Progress Journal
Goal
Keep long-running agent work understandable and resumable.
When to use
Use when work spans multiple sessions, multiple agents, large refactors, uncertain plans, or important decisions.
When not to use
Do not use for tiny one-shot tasks where notes would add noise.
Inputs
Inspect existing CODEX_STATE.md, PLANS.md, DECISIONS.md, issue notes, and recent changed files.
Workflow
- Capture the current objective.
- Record assumptions and constraints.
- Track files touched and why.
- Record decisions that should survive the session.
- Keep plans short and update them as reality changes.
- Mark completed, blocked, and deferred work.
- Remove stale notes when they become misleading.
Journal files
CODEX_STATE.md: current state and next action.PLANS.md: active and proposed implementation plans.DECISIONS.md: durable decisions and rationale.PROJECT_INDEX.md: repo map and commands.
Validation
Verify notes match the actual repository state before finalizing.
Final response
Summarize what changed in notes, current status, and next safe action.
What ships with it
4 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.
- 2mo ago First seen · 51 lines · 31 tokens per session scan A 0f67059f3cdb
codex-progress-journal is a skill published in the GitHub repository YankielDBC2/codex-skills-library (13 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 303 once invoked, about $0.0001 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-progress-journal compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| codex-progress-journalYankielDBC2/codex-skills-library | Skill | 13 | 3mo ago | MIT | A | 31 | Codex |
| planning-with-fileschainlesschain/chainlesschain | Skill | 11 | today | none | A | 36 | Claude Code |
| agent-harness-fault-injectionranbot-ai/awesome-skills | Skill | 8 | yesterday | none | A | 34 | Claude Code, Codex |
| Migratedanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 104 | Claude Code, Codex |
| Cortexdanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 184 | Claude Code |
| Profiledanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 108 | Claude Code, Codex |
| wiki-dashboardAr9av/obsidian-wiki | Skill | 3.7k | yesterday | MIT | A | 42 | Claude Code |