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-l10git 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-l10)<a href="https://agentmods.dev/skills/bradfeld/ceos/ceos-l10"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-l10/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-l10"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-l10.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 254 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.00017 | $0.03340 |
| Opus 5.5 | $0.00007 | $0.01336 |
| Sonnet 5.5 | $0.00003 | $0.00668 |
| Haiku 4.5 | $0.00002 | $0.00334 |
Grade A, and why
ceos-l10 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ceos-l10
Facilitate the Level 10 (L10) Meeting — the weekly 90-minute leadership meeting that keeps the team aligned, accountable, and solving problems. The L10 follows a strict 7-section agenda with time boxes.
When to Use
- "Run L10" or "start our L10"
- "Level 10 meeting" or "weekly meeting"
- "Start our meeting" or "let's do our weekly"
- "Review last week's L10" or "what were our to-dos?"
- Any weekly leadership team meeting
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/meetings/l10/YYYY-MM-DD.md |
L10 meeting notes |
data/scorecard/weeks/ |
Latest scorecard (pulled during Scorecard section) |
data/rocks/[quarter]/ |
Current Rocks (pulled during Rock Review) |
data/issues/open/ |
Open issues (surfaced during IDS section) |
data/meetings/l10/ |
Previous L10s (for To-Do review) |
templates/l10-meeting.md |
Meeting template |
data/accountability.md |
Accountability Chart (seat owners for To-Do assignment validation) |
Meeting Structure (90 minutes)
| # | Section | Time | Purpose |
|---|---|---|---|
| 1 | Segue | 5 min | Personal/professional good news |
| 2 | Scorecard | 5 min | Review weekly numbers |
| 3 | Rock Review | 5 min | Status of quarterly Rocks |
| 4 | Headlines | 5 min | Customer and employee news |
| 5 | To-Do Review | 5 min | Check last week's To-Dos |
| 6 | IDS | 60 min | Identify, Discuss, Solve top issues |
| 7 | Conclude | 5 min | New To-Dos, cascading messages, rating |
Process
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 d32dba2f0a2e
- 1mo ago First seen · 291 lines · 17 tokens per session scan A 26c143cee636
ceos-l10 is a skill published in the GitHub repository bradfeld/ceos (159 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 3,340 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.