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 ZachBeta/claude-as-coach --skill planning-basegit clone --depth 1 https://github.com/ZachBeta/claude-as-coachWrote 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/zachbeta/claude-as-coach/planning-base)<a href="https://agentmods.dev/skills/zachbeta/claude-as-coach/planning-base"><img src="https://agentmods.dev/badge/skills/zachbeta/claude-as-coach/planning-base/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/zachbeta/claude-as-coach/planning-base"><img src="https://agentmods.dev/badge/skills/zachbeta/claude-as-coach/planning-base.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.00110 | $0.02431 |
| Opus 5 | $0.00055 | $0.01215 |
| Sonnet 5 | $0.00022 | $0.00486 |
| Haiku 4.5 | $0.00011 | $0.00243 |
Grade A, and why
planning-base 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 9d 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning (Base Framework)
Core insight: The planning process is the same at any time scale. What changes is the inputs, the time horizon, and the granularity of experiments.
The Core Structure
Every planning session covers:
- Coming From → Where capacity/state is now
- Constraints → What's fixed that we plan around
- Priorities → 2-3 key focuses (max)
- Experiments → What to test/try/explore
- Success Levels → What "good enough" looks like (0-3)
Time Scale as Parameter
| Scale | Inputs | Horizon | Output |
|---|---|---|---|
| Daily | Yesterday's summary | 1 day | Today's focus |
| Weekly | Weekly retro | 7 days | Weekly plan |
| Monthly | Monthly retro | 4 weeks | Monthly plan |
| Quarterly | Quarterly retro | 3 months | Quarterly plan |
| Yearly | Yearly retro | 12 months | Yearly plan |
Natural flow: Retro → Planning at same scale. Insights fresh, immediately inform forward planning.
Process
1. Establish Boundaries
# Verify current date
TZ='America/New_York' date '+%A, %B %d, %Y - %I:%M %p %Z'
Confirm the period being planned:
- Daily: "Planning [Date]. Correct?"
- Weekly: "Planning [Start] - [End]. Correct?"
- Monthly: "Planning [Month Year]. Correct?"
- Quarterly: "Planning Q[X] [Year]. Correct?"
- Yearly: "Planning [Year]. Correct?"
2. Load Context
Load inputs appropriate to scale:
- Daily: Yesterday's summary, today's calendar
- Weekly: This week's retro, monthly goals
- Monthly: This month's retro, quarterly goals
- Quarterly: This quarter's retro, yearly goals
- Yearly: This year's retro, multi-year vision
Purpose: Understand current capacity and context before planning.
3. Identify Constraints FIRST ⚠️ CRITICAL
Before suggesting priorities, identify what's fixed:
Ask about:
- Non-negotiables: Deadlines, appointments, obligations (can't move)
- Known drains: High-effort tasks, energy-intensive work (need buffer)
- Timeline pressures: Reverse-engineering from future dates
- Ongoing experiments: Maintain consistency, don't disrupt data
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.
- 9d ago First seen · 348 lines · 110 tokens per session scan A 013a22df112e
planning-base is a skill published in the GitHub repository ZachBeta/claude-as-coach (5 stars, last pushed 7mo ago), licensed MIT. It adds 110 tokens to every session and 2,431 once invoked, about $0.0006 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…