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 anhnguyen0905/codex-mcp --skill media-planninggit clone --depth 1 https://github.com/anhnguyen0905/codex-mcpWrote 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/anhnguyen0905/codex-mcp/media-planning)<a href="https://agentmods.dev/skills/anhnguyen0905/codex-mcp/media-planning"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/media-planning/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/anhnguyen0905/codex-mcp/media-planning"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/media-planning.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.00068 | $0.00876 |
| Opus 5 | $0.00034 | $0.00438 |
| Sonnet 5 | $0.00014 | $0.00175 |
| Haiku 4.5 | $0.00007 | $0.00088 |
Grade A, and why
media-planning 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 12d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Media Planning (budget allocation across channels)
Allocate on marginal return, not average
The only defensible split equalizes marginal return across channels: keep moving the next dollar to whichever channel returns most at its current spend level, until the returns equalize or the payback bar is hit. Average CPI per channel is the wrong input — it always flatters the small channel.
marginal CPI ≈ Δspend / Δinstalls (measured between adjacent spend levels of the same channel)
scale ceiling = the spend beyond which marginal CPI exceeds the breakeven CPI (see unit-economics)
Every channel saturates. A plan that scales a channel linearly from its current spend is the single most common planning error — the CPI curve bends upward well before the budget runs out.
The plan itself
A media plan is a table, not a paragraph. One row per channel × month:
| channel | month | spend | assumed CPI | expected installs | basis of the CPI assumption | confidence |
- Every CPI assumption must name its basis: last quarter's actual at comparable spend, a test result, or a vendor estimate (mark vendor estimates as unverified).
- Sum to the actual budget and reconcile: plans that don't add up get discovered in month two.
- Show a downside scenario (CPI +20–30%, or the channel not scaling past X) with what gets cut first. A plan without a downside branch is a forecast, not a plan.
Reserve, pacing, seasonality
- Test reserve: hold back roughly 10–20% for new channels/creative/geos. Without it the plan can only ever re-buy last quarter's mix, and the mix decays.
- Pacing: front-load learning (new campaigns need volume to exit the learning phase), then flatten. Month-end spend dumps buy the worst inventory of the month.
- Seasonality: Q4 and local holiday peaks inflate CPM materially; a plan built on Q2 CPMs under-delivers in Q4 at the same budget. Plan the same installs at a higher CPI, or shift timing.
Channel roles differ — don't compare them on CPI alone
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.
- 12d ago First seen · 75 lines · 68 tokens per session scan A ddc1174630b0
media-planning is a skill published in the GitHub repository anhnguyen0905/codex-mcp (3 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 876 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…