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-accountabilitynpx skills add bradfeld/ceos --skill ceos-accountabilitygit 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-accountability)<a href="https://agentmods.dev/skills/bradfeld/ceos/ceos-accountability"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-accountability.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.00023 | $0.03330 |
| Opus 5 | $0.00012 | $0.01665 |
| Sonnet 5 | $0.00005 | $0.00666 |
| Haiku 4.5 | $0.00002 | $0.00333 |
Grade A, and why
ceos-accountability 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ceos-accountability
Manage the Accountability Chart — the organizational structure that defines who owns what seat, what each seat's 5 key responsibilities are, and the reporting hierarchy. Every function of the business has one clear owner. A person can own multiple seats, but every seat needs exactly one owner.
When to Use
- "Show the accountability chart" or "who owns what?"
- "Update the org chart" or "change seat ownership"
- "Add a new seat" or "we need a VP of Product"
- "Remove a seat" or "consolidate these roles"
- "Audit the accountability chart" or "check for gaps"
- "Who reports to whom?" or "show the structure"
- "How many seats does [person] own?"
- "Are there any empty seats?" or "what roles are unfilled?"
- "Update roles for [seat]" or "change responsibilities"
- Any discussion about organizational structure, seat ownership, or role definition
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/accountability.md |
The Accountability Chart (source of truth) |
templates/accountability.md |
Template for new charts (used by setup.sh init) |
data/people/ |
Person evaluation files (cross-reference for Audit) |
Accountability Chart Structure
The chart is a single markdown file (data/accountability.md) with this structure:
- Company heading:
## CompanyNameat the top with a*Last updated: YYYY-MM-DD*line - How to Use section: Instructions block (preserved during edits)
- Seats: Each seat is a
## SeatNameheading followed by:**Owner:** PersonName(or[Name]if unfilled)- A roles table with exactly 5 numbered rows
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 · 334 lines · 23 tokens per session scan A 7d6496b3c5ff
ceos-accountability is a skill published in the GitHub repository bradfeld/ceos (145 stars, last pushed 27d ago), licensed MIT. It adds 23 tokens to every session and 3,330 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…