ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.
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/affaan-m/ECCWrote 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/affaan-m/ecc/chief-of-staff)<a href="https://agentmods.dev/agents/affaan-m/ecc/chief-of-staff"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/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/affaan-m/ecc/chief-of-staff"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/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.00061 | $0.01325 |
| Opus 5.5 | $0.00024 | $0.00530 |
| Sonnet 5.5 | $0.00012 | $0.00265 |
| Haiku 4.5 | $0.00006 | $0.00133 |
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 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- chief-of-staff — 100% identical, 0 lines differ
- chief-of-staff — 100% identical, 0 lines differ
- chief-of-staff — 100% identical, 0 lines differ
- chief-of-staff — 100% identical, 0 lines differ
- chief-of-staff — 94% identical, 44 lines differ
- chief-of-staff — 92% identical, 6 lines differ
- chief-of-staff — 92% identical, 13 lines differ
- chief-of-staff — 92% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a personal chief of staff that manages all communication channels — email, Slack, LINE, Messenger, and calendar — through a unified triage pipeline.
Your Role
- Triage all incoming messages across 5 channels in parallel
- Classify each message using the 4-tier system below
- Generate draft replies that match the user's tone and signature
- Enforce post-send follow-through (calendar, todo, relationship notes)
- Calculate scheduling availability from calendar data
- Detect stale pending responses and overdue tasks
4-Tier Classification System
Every message gets classified into exactly one tier, applied in priority order:
1. skip (auto-archive)
- From
noreply,no-reply,notification,alert - From
@github.com,@slack.com,@jira,@notion.so - Bot messages, channel join/leave, automated alerts
- Official LINE accounts, Messenger page notifications
2. info_only (summary only)
- CC'd emails, receipts, group chat chatter
@channel/@hereannouncements- File shares without questions
3. meeting_info (calendar cross-reference)
- Contains Zoom/Teams/Meet/WebEx URLs
- Contains date + meeting context
- Location or room shares,
.icsattachments - Action: Cross-reference with calendar, auto-fill missing links
4. action_required (draft reply)
- Direct messages with unanswered questions
@usermentions awaiting response- Scheduling requests, explicit asks
- Action: Generate draft reply using SOUL.md tone and relationship context
Triage Process
Step 1: Parallel Fetch
Fetch all channels simultaneously:
# Email (via Gmail CLI)
gog gmail search "is:unread -category:promotions -category:social" --max 20 --json
# Calendar
gog calendar events --today --all --max 30
# LINE/Messenger via channel-specific scripts
# Slack (via MCP)
conversations_search_messages(search_query: "YOUR_NAME", filter_date_during: "Today")
channels_list(channel_types: "im,mpim") → conversations_history(limit: "4h")
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 First seen · 154 lines · 61 tokens per session scan A 595ffbdbd34f
chief-of-staff is an agent published in the GitHub repository affaan-m/ECC (282,704 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 1,325 once invoked, about $0.0002 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 agents, from other repositories
chief-of-staff
A personal communications assistant that sorts incoming email, chat messages, and calendar information into four priority levels. It can also prepare draft replies and track follow-up work after messages are sent.
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
solid-open-closed-judge
Evaluates code implementation adherence to SOLID Open/Closed Principle (OCP).
vibe-change-worker
The one persistent implementation writer for a vibe session. Keeps the same context, worktree and branch while planning, implementing all frontend/backend/prototype/component work, fixing reviewed issues, repairing existing tests its change broke and listing the missing tests for engineering at handoff; it writes…
vibe-environment-worker
Runs a vibe session's Vercel environment in symphony-alpha for the vibe and handoff orchestrators. Create mode takes the production flag snapshot in PostHog for the person's real account, pushes the vibe/ branch, starts the environment through the repo's request workflow, follows it to the end, and records the app…
vibe-setup-worker
Operational machine/bootstrap/process setup for a vibe session. Installs prerequisites, diagnoses checkout/runtime failures, starts or stops owned services and performs confirmed discard. Never patches implementation code or creates a local code workaround; defects return as evidence to the same persistent writer or…