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-rocksgit 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-rocks)<a href="https://agentmods.dev/skills/bradfeld/ceos/ceos-rocks"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-rocks/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-rocks"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-rocks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00015 | $0.03587 |
| Opus 5.5 | $0.00006 | $0.01435 |
| Sonnet 5.5 | $0.00003 | $0.00717 |
| Haiku 4.5 | $0.00002 | $0.00359 |
Grade A, and why
ceos-rocks 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ceos-rocks
Manage quarterly Rocks — the 3-7 most important priorities for the next 90 days. Each Rock has one owner, a measurable outcome, and a due date at quarter end.
When to Use
- "Set rocks for this quarter" or "let's plan our quarterly priorities"
- "Rock status" or "how are our rocks tracking?"
- "Score rocks" or "end of quarter review"
- "Create a rock" or "add a new rock for [person]"
- "What rocks does [person] own?"
- Any quarterly planning or review conversation
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/rocks/QUARTER/ |
Rock files for each quarter (e.g., data/rocks/2026-Q1/) |
data/vision.md |
V/TO document (1-Year Plan for alignment checks) |
templates/rock.md |
Template for creating new Rock files |
data/accountability.md |
Accountability Chart (seat owners for Rock-owner alignment) |
Rock File Format
Each Rock is a markdown file with YAML frontmatter:
id: rock-001
title: "Launch Beta Program"
owner: "brad"
quarter: "2026-Q1"
status: on_track # on_track | off_track | complete | dropped
created: "2026-01-02"
due: "2026-03-31"
Status values:
on_track— progressing as expectedoff_track— behind or at riskcomplete— done (set during end-of-quarter scoring)dropped— no longer a priority (set during end-of-quarter scoring)
File naming: rock-NNN-slug.md where NNN is a zero-padded ID and slug is the title slugified (lowercase, hyphens, no special chars).
Milestones: Rocks support two milestone formats:
- Structured (frontmatter): Array of milestone objects with
title, optionalduedate, andstatus(todo/in_progress/done). Enables date-based progress tracking and overdue detection. - Markdown checklist (body): Traditional
- [ ]/- [x]checklist items in the Milestones section. Simple and human-friendly.
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 Changed · +48 lines 5ffd72ae0658
- 1mo ago First seen · 275 lines · 15 tokens per session scan A 2b37d37e9dab
ceos-rocks is a skill published in the GitHub repository bradfeld/ceos (159 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 3,587 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-08-30.
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.