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 ooiyeefei/ccc --skill daily-chiefgit clone --depth 1 https://github.com/ooiyeefei/cccWrote 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/ooiyeefei/ccc/daily-chief)<a href="https://agentmods.dev/skills/ooiyeefei/ccc/daily-chief"><img src="https://agentmods.dev/badge/skills/ooiyeefei/ccc/daily-chief.svg" alt="Measured on agentmods" 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.00029 | $0.00485 |
| Opus 5 | $0.00015 | $0.00243 |
| Sonnet 5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
daily-chief 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 8d 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.
What it actually says
Daily Chief
Remote truth. Visual preview. Explicit apply.
Use this workflow only when the user invokes /daily-chief or /skill:daily-chief. Only Plan today is implemented. Daily Chief is the remote source of truth. The local HTML file is a visual preview, never task or plan state.
-
Check authentication. If credentials are missing or rejected, run browser device login and wait for approval.
npx [email protected] status --json npx [email protected] auth -
Read the request and prior conversation. Ask only for missing canonical answers: available hours, energy (
high,normal, orlow), must happen today, fixed events, and what can defer. -
Create the remote, non-mutating preview.
dateis optional and the server chooses its current UTC date when omitted.npx [email protected] plan-today --answers-json '{"availableHours":4,"energy":"normal","mustHappen":"Ship the review","fixedEvents":"15:00 client call","canDefer":"Inbox cleanup"}' --json -
Inspect the returned local HTML
outfile and its recommendations. It is local only and has no token. Do not publish it or use htmldrop. -
Require clear confirmation to apply that exact preview. Viewing it, silence, or a vague acknowledgment is not confirmation.
-
Apply only the returned
applyPayload, unchanged. It contains the storedpreviewIdand its generatedidempotencyKey.npx [email protected] apply-plan --json '<applyPayload from plan-today>' --output-json
Report an applied plan only after the command receives a successful remote response. Never expose, log, or embed bearer tokens. For API semantics and self-host configuration, read the API reference.
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.
- 8d ago First seen · 40 lines · 29 tokens per session scan A 5c0bf635ee70
daily-chief is a skill published in the GitHub repository ooiyeefei/ccc (486 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 485 once invoked, about $0.0001 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.