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-calendargit 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-calendar)<a href="https://agentmods.dev/skills/bradfeld/ceos/ceos-calendar"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-calendar/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-calendar"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-calendar.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.00025 | $0.01872 |
| Opus 5.5 | $0.00010 | $0.00749 |
| Sonnet 5.5 | $0.00005 | $0.00374 |
| Haiku 4.5 | $0.00003 | $0.00187 |
Grade A, and why
ceos-calendar 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ceos-calendar
Manage the rolling 6-month market calendar — external events, partner milestones, fundraising deadlines, and team constraints that affect quarterly planning and Rocks.
When to Use
- "Show the calendar" or "market calendar"
- "Add an event" or "add a conference to the calendar"
- "What events are coming up?" or "upcoming deadlines"
- "Update event status" or "mark that event as past"
- "Calendar for quarterly planning" or "what's happening next quarter?"
- "Any constraints this month?" or "team availability"
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/calendar/events.md |
Market calendar events (dates, types, owners, status) |
templates/calendar-events.md |
Template for initial calendar file |
data/vision.md |
Strategic context for event relevance |
data/rocks/QUARTER/ |
Current Rocks for alignment checks |
data/accountability.md |
Seat owners for event-owner validation |
Calendar Data Format
Events are stored in a single markdown table in data/calendar/events.md. Each row is one event:
| Field | Type | Required | Description |
|---|---|---|---|
| Date | YYYY-MM-DD |
Yes | Event date (ISO 8601) |
| Event | string | Yes | Short event name |
| Type | enum | Yes | partner, market, fundraising, constraint |
| Owner | string | Yes | Person responsible, or "Team" for constraints |
| Status | enum | Yes | upcoming, past, cancelled |
| Notes | string | No | Brief context or outcome |
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 fab2e5ef32b4
- 1mo ago First seen · 210 lines · 25 tokens per session scan A bb650c453e23
ceos-calendar is a skill published in the GitHub repository bradfeld/ceos (159 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 1,872 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.