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-trendsgit 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-trends)<a href="https://agentmods.dev/skills/bradfeld/ceos/ceos-trends"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-trends.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.00030 | $0.05352 |
| Opus 5 | $0.00015 | $0.02676 |
| Sonnet 5 | $0.00006 | $0.01070 |
| Haiku 4.5 | $0.00003 | $0.00535 |
Grade A, and why
ceos-trends 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 7d 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 — 527 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ceos-trends
Longitudinal EOS health tracking - analyze how your organization is improving over time across all Six Key Components. While ceos-dashboard shows today's snapshot, ceos-trends answers the question every EOS coach asks: "Are we getting better?"
When to Use
- "How are we trending?" or "show our progress"
- "Are we improving?" or "EOS health over time"
- "Quarter comparison" or "compare Q1 to Q2"
- "Rock completion history" or "how have our rocks been?"
- "Scorecard trends" or "are our numbers improving?"
- "Show trends" or "progress report"
- Before quarterly planning or annual planning for historical context
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/YYYY-QN/ |
Rock files per quarter (status, owner, milestones) |
data/scorecard/weeks/YYYY-WNN.md |
Weekly scorecard entries (metrics, on/off track) |
data/scorecard/metrics.md |
Metric definitions (goals, thresholds) |
data/checkups/YYYY-MM-DD.md |
Organizational Checkup results (component scores) |
data/issues/open/ |
Currently open issues (priority, created date) |
data/issues/solved/ |
Resolved issues (priority, created date, resolution) |
data/todos/ |
To-Do files (status, created, completed_on, source) |
data/meetings/l10/YYYY-MM-DD.md |
L10 meeting notes (one per meeting) |
Design Principles
- Read-only. Trends never modifies any data files. It reads, calculates, and reports.
- Graceful degradation. Works with whatever data exists. One quarter of Rocks? Show that. No checkups yet? Skip that section with guidance. Never error on missing data.
- Cross-skill coordination. Each trend section suggests the relevant skill for taking action. Trends shows the trajectory; other skills change it.
- Minimum data threshold. For meaningful trends, at least 2 data points are needed (e.g., 2 quarters of Rocks, 2 checkups). With only 1 data point, show the baseline value and note: "More data needed for trend analysis."
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.
- 7d ago First seen · 527 lines · 30 tokens per session scan A 7ed7b0dae663
ceos-trends is a skill published in the GitHub repository bradfeld/ceos (145 stars, last pushed 28d ago), licensed MIT. It adds 30 tokens to every session and 5,352 once invoked, about $0.0002 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.