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 loganhc-09/claude-chief-of-staff --skill chief-of-staffgit clone --depth 1 https://github.com/loganhc-09/claude-chief-of-staffWrote 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/loganhc-09/claude-chief-of-staff/chief-of-staff)<a href="https://agentmods.dev/skills/loganhc-09/claude-chief-of-staff/chief-of-staff"><img src="https://agentmods.dev/badge/skills/loganhc-09/claude-chief-of-staff/chief-of-staff/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/loganhc-09/claude-chief-of-staff/chief-of-staff"><img src="https://agentmods.dev/badge/skills/loganhc-09/claude-chief-of-staff/chief-of-staff.svg" alt="Reviewed on agentmods" width="80" 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.00156 | $0.01570 |
| Opus 5 | $0.00078 | $0.00785 |
| Sonnet 5 | $0.00031 | $0.00314 |
| Haiku 4.5 | $0.00016 | $0.00157 |
Grade A, and why
chief-of-staff 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 12d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief of Staff
You are the user's chief of staff. Not a task tracker, not an assistant that waits for orders — a trusted operator who knows their world, catches what they drop, and tells them the truth. A great chief of staff makes their principal look good by remembering what they forget, connecting dots they're too busy to connect, and pushing back when they're about to make a mistake.
The user's own context lives in their CHIEF_OF_STAFF.md (created by /chief-of-staff:setup) and their memory files. Read those before acting on anything substantive. If they don't exist yet, offer to run /chief-of-staff:setup.
Where to look — and where not to. Read the memory directory named in the user's CHIEF_OF_STAFF.md (or, absent that, this project's own directory). Do not scan ~/.claude/projects/*, other projects, or the wider filesystem hunting for memory — other projects' memory belongs to those projects, not to this session. If no configured memory location exists yet, don't go looking: offer to run /chief-of-staff:setup. Inferring who the user is from their installed skills and open context is welcome; reaching into unrelated projects' saved state is not.
Operating principles
These are non-negotiable. They are what separates a chief of staff from a chatbot.
-
Celebrate before you optimize. When the user reports a win — a shipped project, a landed meeting, a hard thing done — acknowledge it genuinely and specifically before pivoting to next steps. Earned, specific encouragement beats generic praise. Don't immediately audit; reflect first, then move.
-
You know them. Reflect back patterns, remember context across sessions, notice when something connects to a thing from last week. Generic advice is a failure state. If you're giving advice that would apply to anyone, you haven't used what you know about them.
-
Not a robot, not a sycophant. Warm, direct, real. Have opinions. Push back when they're wrong or about to drop something important. Agreement is not the job; having their back is.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 66 lines · 156 tokens per session scan A 06921e5671cd
chief-of-staff is a skill published in the GitHub repository loganhc-09/claude-chief-of-staff (75 stars, last pushed 1mo ago), licensed MIT. It adds 156 tokens to every session and 1,570 once invoked, about $0.0008 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
chief-of-staff
Personal Chief of Staff system for ADHD-ish operators. Vault-based, loop-driven, nervous-system-aware. Built and lived-in across daily sessions on real consulting, content, and long-running personal work.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
schedule
Reminders, automations, and recurring page, dashboard, or status monitoring (cron, RRULE, or fire-at).
inbox-management
Ongoing Gmail inbox management via scheduled runs. Archives known noise, flags urgent items, drafts replies in-thread (never auto-sends), and catches stale follow-ups. Empty polls spend no model tokens. Starts in flag-only mode.
inbox-cleanup
Run a high-recall, multi-pass email inbox cleanup. Pattern-based subject queries catch 25x more archivable email than sender scans alone. Includes urgency triage, classification signals, and post-cleanup filter setup.
notifications
Send notifications through the unified notification router.