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 agentmods add skills/bradfeld/ceos/ceos-checkupnpx skills add bradfeld/ceos --skill ceos-checkupgit 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-checkup)<a href="https://agentmods.dev/skills/bradfeld/ceos/ceos-checkup"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-checkup.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.00021 | $0.05759 |
| Opus 5 | $0.00010 | $0.02880 |
| Sonnet 5 | $0.00004 | $0.01152 |
| Haiku 4.5 | $0.00002 | $0.00576 |
Grade A, and why
ceos-checkup 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 6d 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 — 525 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ceos-checkup
Measure organizational health using the standard EOS Organizational Checkup — a 20-question assessment across the Six Key Components (Vision, People, Data, Issues, Process, Traction). Each leadership team member rates the organization 1-5 on each question, and scores are calculated per component and overall. Use quarterly or semi-annually to track progress and surface alignment gaps.
Not for: Individual team member evaluation (use ceos-people), V/TO refresh (use ceos-annual), or quarterly Rock setting (use ceos-quarterly-planning).
When to Use
- "Run the organizational checkup" or "let's do the EOS checkup"
- "How healthy is the organization?" or "team health assessment"
- "Score the six key components" or "rate our EOS components"
- "Show checkup history" or "review past checkups"
- "Compare team ratings" or "show alignment gaps"
- "Are we improving on Vision/People/Data/Issues/Process/Traction?"
- Any discussion about overall organizational health, EOS component scores, or team alignment
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/checkups/ |
Checkup result files (one per session, dated) |
templates/checkup.md |
Template for new checkup files |
data/vision.md |
V/TO — Core Values, Core Focus, targets (read-only) |
data/accountability.md |
Accountability Chart — team structure and seats (read-only) |
data/rocks/ |
Quarterly Rocks for Traction context (read-only) |
data/scorecard/ |
Weekly metrics for Data context (read-only) |
data/people/ |
People evaluations for People context (read-only) |
data/issues/ |
Open/resolved issues for Issues context (read-only) |
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.
- 6d ago First seen · 525 lines · 21 tokens per session scan A 4968cff92590
ceos-checkup is a skill published in the GitHub repository bradfeld/ceos (145 stars, last pushed 27d ago), licensed MIT. It adds 21 tokens to every session and 5,759 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…
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…