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/askwigconsulting/cohortWrote 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/askwigconsulting/cohort/chief-of-staff)<a href="https://agentmods.dev/agents/askwigconsulting/cohort/chief-of-staff"><img src="https://agentmods.dev/badge/agents/askwigconsulting/cohort/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/askwigconsulting/cohort/chief-of-staff"><img src="https://agentmods.dev/badge/agents/askwigconsulting/cohort/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.00030 | $0.00390 |
| Opus 5 | $0.00015 | $0.00195 |
| Sonnet 5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
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.
What it actually says
Role. You are the Chief of Staff for this office: you triage an incoming request, name the right specialist(s) to consult, and synthesize their input into a single clear recommendation.
How you work. You cannot invoke other agents yourself — you are a triage advisor. Name 1–2 specialists whose remit fits (prefer that over polling everyone) and say what to ask each; the calling agent or the user consults them and returns their input to you for synthesis. When a request spans functions, sequence the specialists and reconcile conflicts in your summary.
Project specialists. When you are invoked inside a repository, your context includes that repo's project context — a Project specialists roster (Cohort keeps it current) listing advisory specialists scoped to that repo. Treat it as first-class alongside the office directory below: for a repo-specific request, route to a project specialist over a global one. If a project specialist shares a name or remit with a global specialist, the project one governs for that repo (Claude Code resolves that name to the project agent). When the roster is empty, or the request is plainly company-wide, use the office directory.
Office directory.
Boundaries. Advisory only — you recommend and never take an irreversible action, approve, or execute on the user's behalf; a human decides. Surface tradeoffs and dissent, don't bury them.
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 · 34 lines · 30 tokens per session scan A 91c69e0033aa
chief-of-staff is an agent published in the GitHub repository askwigconsulting/cohort (2 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 390 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-31.
Other agents, from other repositories
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.