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-assistancegit 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-assistance)<a href="https://agentmods.dev/skills/bradfeld/ceos/ceos-assistance"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-assistance/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-assistance"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-assistance.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.00021 | $0.03720 |
| Opus 5.5 | $0.00008 | $0.01488 |
| Sonnet 5.5 | $0.00004 | $0.00744 |
| Haiku 4.5 | $0.00002 | $0.00372 |
Grade A, and why
ceos-assistance 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 1mo 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 — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ceos-assistance
Manage the daily operational delegation workflow between a leader and their assistant using "The Stack" — a batch delegation queue. This skill implements the 5 disciplines of The Assistance Track: batching, The Stack, the daily meeting, the assistant's judgment, and a weekly review. It complements ceos-delegate, which handles strategic delegation (what SHOULD be delegated), by managing operational delegation (HOW items are delegated day-to-day).
Not for: Strategic delegation decisions (use ceos-delegate), task tracking without a leader-assistant relationship (use ceos-todos), or meeting facilitation (use ceos-l10). The Assistance Track is specifically about the daily delegation workflow between a leader and their dedicated assistant.
When to Use
- "Add to the stack" or "stack this for my assistant"
- "Run the daily meeting" or "daily standup with my assistant"
- "Review the stack" or "what's on the stack?"
- "Weekly assistance review" or "how's delegation going this week?"
- "Show stuck items" or "what's been on the stack too long?"
- "Hand off [item] to [assistant]" or "mark [item] as done"
- Any discussion about daily delegation queues, assistant standups, or The Assistance Track
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/assistance/stack/ |
Stack items — one file per delegation item |
data/assistance/daily/ |
Daily meeting logs — one file per meeting |
templates/assistance-stack.md |
Template for new stack items |
templates/assistance-daily.md |
Template for daily meeting logs |
data/accountability.md |
Source of leader-assistant relationships (read-only — use ceos-accountability to modify) |
data/delegate/ |
Delegate and Elevate audits (read-only — reference for delegation context) |
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.
- 1mo ago First seen · 383 lines · 21 tokens per session scan A 6c77ef94b92a
ceos-assistance is a skill published in the GitHub repository bradfeld/ceos (159 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 3,720 once invoked, about $0.0001 per session on Opus 5.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-09-14.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.