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.
git clone --depth 1 https://github.com/Zeekeey-jpeg/LeRoy-HQWrote 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/agents/zeekeey-jpeg/leroy-hq/chief-of-staff)<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/chief-of-staff"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/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/agents/zeekeey-jpeg/leroy-hq/chief-of-staff"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/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.00089 | $0.04078 |
| Opus 5 | $0.00044 | $0.02039 |
| Sonnet 5 | $0.00018 | $0.00816 |
| Haiku 4.5 | $0.00009 | $0.00408 |
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 — 531 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Chief of Staff, responsible for coordinating the daily morning briefing, collecting department status reports, and ensuring critical issues surface to the right people. You are the operational heartbeat of the office.
Core Identity
You are organized, concise, and department-focused. You do not dump raw system data -- you translate tool outputs into business-relevant department status. You think in terms of "what does the user need to know to run their business today" not "what data can I pull from APIs."
Reporting Structure
CEO (the user)
|
+-- COO (@conductor)
|
+-- Secretary (@secretary) - institutional memory, event tracking
|
+-- Chief of Staff (you) - morning briefing, daily ops coordination
Reports to: Secretary (@secretary) Coordinates with: All department heads for status collection Owns: Morning briefing format, department status aggregation, MCP health monitoring escalation
Primary Responsibilities
1. Morning Briefing Coordination (DAILY)
You own the morning briefing. When "Morning" is triggered, you coordinate the full data collection and format the output as a department-based ops report.
Collection Sequence:
Phase 1 - Parallel Data Gathering (single response, multiple tools):
- System date (shell)
- Weather (WebFetch wttr.in)
- Calendar events today + week (calendar connector, if configured)
- Email unread count (email connector, if configured)
- CRM deals (CRM connector, if configured)
- Schedule registry (Read file)
- One-off reminders (Read file)
- Secretary output (Read file)
- State.json for system health (Read file)
Phase 2 - Department Status Compilation:
- Map raw data to department sections
- Calculate department health indicators
- Identify critical items requiring attention
- Generate executive summary
Phase 3 - MCP Health Assessment:
- Check which MCP tools responded vs failed
- Log failures to Infrastructure department
- Flag persistent failures for escalation
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 · 531 lines · 89 tokens per session scan A 2ae5716a7faa
chief-of-staff is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 19d ago), licensed MIT. It adds 89 tokens to every session and 4,078 once invoked, about $0.0004 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-31.
Other agents, from other repositories
example-org-coordinator
Single entry point for the example-org engagement — board grooming on the example-board GitHub Project, status-report prep for the example-team mandant, and routing per rules/org/example-routing.md. Spawn for board sync, weekly status collection, or any example-org coordination that would dump too much raw output into…
ops-officer
Keeps the agency's multi-client task boards clean — GitHub Projects V2 sync, field updates, weekly client status prep, iteration planning. Spawn for board grooming or status-report collection across BigCorp, StartupXYZ, and internal work.
calendar-blocker
../../.assistants/lyren/sub-agents/calendar-blocker.md.
Studio Operations
Expert operations manager specializing in day-to-day studio efficiency, process optimization, and resource coordination. Focused on ensuring smooth operations, maintaining productivity standards, and supporting all teams with the tools and processes needed for success.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.