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 ucsahinn/codex-chef --skill context-budget-plannergit clone --depth 1 https://github.com/ucsahinn/codex-chefWrote 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/ucsahinn/codex-chef/context-budget-planner)<a href="https://agentmods.dev/skills/ucsahinn/codex-chef/context-budget-planner"><img src="https://agentmods.dev/badge/skills/ucsahinn/codex-chef/context-budget-planner.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.00053 | $0.00618 |
| Opus 5 | $0.00026 | $0.00309 |
| Sonnet 5 | $0.00011 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
context-budget-planner 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 7d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Budget Planner
Use this skill before broad, long-running, or multi-source Codex work. The goal is to keep useful capability while reducing wasted context.
Output
Return:
- Objective and completion evidence
- Must-load context
- Defer-until-needed context
- Ignore or exclude list
- Tool and source routing
- Token-saving tactics
- Compaction-safe handoff
- Verification gates
Reference Routing
Read references/context-strategy.md for broad repo work, research-heavy
tasks, multi-agent delegation, long command outputs, compaction handoffs,
surface-routing decisions, or token/context tradeoffs.
Rules
- Preserve user constraints, approval gates, file paths, exact commands, and named artifacts.
- Prefer current files and command outputs over memory or guesses.
- Load indexes, manifests, catalogs, and summaries before full files when that still gives reliable evidence.
- Read a selected authoritative instruction file completely before acting on it.
- Do not paste huge logs into the main thread. Summarize the key lines and keep command names exact.
- Do not move secrets, tokens, auth files, session data, private memory, or private local paths into prompts, docs, diagrams, or issue comments.
- Use subagents for bounded read-heavy work only when they reduce noise or produce clearer evidence.
- Put durable behavior in the right surface: prompt,
AGENTS.md, skill, plugin, MCP, hook, memory, rule, config, or script. - Use current official docs or verified sources when external facts affect the answer.
- Keep overlapping optional skills discoverable, but prefer the smallest default set that covers the task without duplicate trigger noise.
Context Budget Template
Objective:
- ...
Completion evidence:
- ...
Must load now:
- ...
Defer until needed:
- ...
Ignore/exclude:
- ...
Tool/source routing:
- Local repo:
- Official docs:
- External docs:
- Browser/UI:
- Security/release:
Token-saving tactics:
- Start from indexes/manifests/catalogs before full files.
- Read only the relevant sections after symbol or text search.
- Summarize long command output instead of copying it wholesale.
- Keep exact commands, paths, versions, and failures.
Compaction handoff:
- Current decision:
- Files changed or inspected:
- Commands run:
- Known blockers:
- Next verification:
Verification gates:
- ...
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.
- 7d ago First seen · 100 lines · 53 tokens per session scan A 061ca05e4c5a
context-budget-planner is a skill published in the GitHub repository ucsahinn/codex-chef (6 stars, last pushed 20d ago), licensed MIT. It adds 53 tokens to every session and 618 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-31.
Other skills, from other repositories
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.
briefing-vault
Initialize, manage, and search the per-project .briefing/ vault. Obsidian-compatible persistent knowledge base.
do-it-context
Use when project terms, relationships, or invariants drift between user language, docs, and implementation.
tfx-index
A project indexer that scans a software project and creates a compact map of its files and metadata. The map can be read later instead of repeatedly examining the whole project.
retro
Record durable lessons, null results, and footguns after hard work or debugging. Use when the user asks for a retro, dead ends need preserving, a task disproves an approach, or "จดบทเรียน". Keep repo knowledge separate from machine-local memory.