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 agentmods add skills/yankieldbc2/codex-skills-library/codex-progress-journalnpx skills add YankielDBC2/codex-skills-library --skill codex-progress-journalgit clone --depth 1 https://github.com/YankielDBC2/codex-skills-libraryWhat 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 | $0.00031 | $0.00303 |
| Opus 5 | $0.00015 | $0.00151 |
| Sonnet 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 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.
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.
- 3d 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 (10 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 303 once invoked, about $0.0002 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
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-obsidian-claude-gradient
OpenDesign's enterprise AI-adoption brief: local-first agents at work, the risk controls, the ROI, and the rollout plan. Built as a decision-grade AI literacy deck for leadership, IT, security.
html-ppt-tech-sharing
OpenDesign internals: how the agent stream, sandbox, and artifacts work — an engineering deep-dive talk. Built as a decision-grade AI literacy deck for engineers, dev community.
vs-user-onboarding
Guide a brand-new SearchCLI/vs user from first-time usage questions to sign-up, purchase of Viking AI Search, AK/SK setup, and a working authenticated CLI. Use when the user says they downloaded or installed SearchCLI/vs and asks how to use it, how to start, sign up, buy, or onboard.
workflow
Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCode, and Grok use…
agent-sop-author
Create (or update) and validate Agent SOPs (Standard Operating Procedures) - markdown-based workflows that guide AI agents through complex, multi-step tasks with RFC 2119 constraints.