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 bradfeld/ceos --skill ceos-quarterly-planninggit clone --depth 1 https://github.com/bradfeld/ceosWrote 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/bradfeld/ceos/ceos-quarterly-planning)<a href="https://agentmods.dev/skills/bradfeld/ceos/ceos-quarterly-planning"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-quarterly-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/bradfeld/ceos/ceos-quarterly-planning"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-quarterly-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 447 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00020 | $0.05608 |
| Opus 5 | $0.00010 | $0.02804 |
| Sonnet 5 | $0.00004 | $0.01122 |
| Haiku 4.5 | $0.00002 | $0.00561 |
Grade A, and why
ceos-quarterly-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 11d 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 — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ceos-quarterly-planning
Facilitate the EOS Quarterly Planning Session — the structured half-day meeting where the leadership team scores outgoing Rocks, reviews Scorecard trends, confirms vision alignment, tackles issues via IDS, and sets the next quarter's Rocks. This is "quarterly pulsing" — the bridge between weekly L10 meetings and the Annual Planning session.
When to Use
- "Run quarterly planning" or "quarterly planning session"
- "Plan next quarter" or "let's plan Q2"
- "Score rocks and plan next quarter"
- "End of quarter review and planning"
- "Quarterly session" or "quarterly pulse"
- "Review the quarter and set new rocks"
- Any leadership team meeting focused on transitioning between quarters
Not for: 1-on-1 quarterly conversations (use ceos-quarterly), annual planning with V/TO refresh (use ceos-annual), or weekly meetings (use ceos-l10).
Context
Finding the CEOS Repository
Search upward from the current directory for the .ceos marker file. This file marks the root of the CEOS repository.
If .ceos is not found, stop and tell the user: "Not in a CEOS repository. Clone your CEOS repo and run setup.sh first."
Sync before use: Once you find the CEOS root, run git -C <ceos_root> pull --ff-only --quiet 2>/dev/null to get the latest data from teammates. If it fails (conflict or offline), continue silently with local data.
Key Files
| File | Purpose |
|---|---|
data/quarterly/YYYY-QN-planning.md |
Quarterly planning session notes (one per quarter) |
data/rocks/YYYY-QN/ |
Rock files for each quarter (read for scoring and reference) |
data/scorecard/weeks/ |
Weekly scorecard data (read for 13-week trend analysis) |
data/scorecard/metrics.md |
Scorecard metric definitions (reference for targets) |
data/vision.md |
V/TO document (read 1-Year Plan for Rock alignment) |
data/issues/open/ |
Open issues (read for IDS sweep) |
data/issues/solved/ |
Solved issues (count for quarter summary) |
templates/quarterly-planning.md |
Template for new quarterly planning files |
data/accountability.md |
Accountability Chart (seat owners for Rock-owner alignment) |
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.
- 11d ago First seen · 496 lines · 20 tokens per session scan A 87c7692ab4e2
ceos-quarterly-planning is a skill published in the GitHub repository bradfeld/ceos (146 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 5,608 once invoked, about $0.0001 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-30.
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…