Skip to content

rlaope/oh-my-hermes / skills/omh-context-budget-review

omh-context-budget-review

Verified

[omh] Context window or token budget at risk: plan compact context, token/cost budgets, summarization checkpoints, and overflow recovery before long agent work. Use when the user says: context-budget-review, context budget review, context budget, token budget review, token budget, prompt budget, prompt caching, prompt cache.

FileKindSize
SKILL.mdskill md9.8 KB
references/cache-placement.mdmarkdown1.8 KB
references/route-capacity.mdmarkdown5.2 KB

references/cache-placement.md

View on GitHub
# Cache Placement Discipline

Every major serving stack caches prompt prefixes by exact bytes: Anthropic prefix caching (explicit breakpoints, discounted reads), OpenAI automatic prefix caching, Gemini implicit caching, DeepSeek context caching. A single changed byte at position N re-bills everything at and after N. OMH never calls a provider; this card disciplines the text OMH generates and the guidance it prepares for the host.

## Placement rules

1. **Stable prefix ordering.** Assemble every instruction surface in a fixed section order, most-stable content first. Regeneration must be byte-stable: same inputs, same bytes.
2. **Volatile bytes never above the fold.** Dates, token counts, git state, status lines, and per-session values never belong in files loaded at session start; they ride the first user turn or the message tail.
3. **Changes travel as appended messages.** Mid-run skill, state, or instruction changes are appended conversation messages, never edits to the system prompt or to a session-start file — a mid-run system-prompt rewrite rebuilds the whole cache (the failure mode behind NousResearch/hermes-agent#13631 and #4319).
4. **Tool surface stays stable mid-session.** Choose the tool set at session start; avoid mid-session connect/disconnect of tool servers; prefer deferred tool loading where the host supports it; serialize tool payloads deterministically (sorted keys).
5. **Fan-outs share a byte-identical preamble.** Sibling prompts lead with the same shared bytes, unit-specific content appended after; stagger dispatch so the first request writes the cache the siblings read.

## Evidence boundary

Cache hit and creation counters are provider or host telemetry. Never claim a hit rate, a saving, or "cache-safe" as observed fact without the host's usage counters; prepared placement is prepared_not_observed.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall