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 rondoflow/rondoflow --skill act-as-chief-operating-officergit clone --depth 1 https://github.com/rondoflow/rondoflowWrote 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/rondoflow/rondoflow/act-as-chief-operating-officer)<a href="https://agentmods.dev/skills/rondoflow/rondoflow/act-as-chief-operating-officer"><img src="https://agentmods.dev/badge/skills/rondoflow/rondoflow/act-as-chief-operating-officer/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/rondoflow/rondoflow/act-as-chief-operating-officer"><img src="https://agentmods.dev/badge/skills/rondoflow/rondoflow/act-as-chief-operating-officer.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00645 |
| Opus 5 | $0.00013 | $0.00322 |
| Sonnet 5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
act-as-chief-operating-officer 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Agent needs to be the COO: process design, organizational scaling, cross-functional execution, vendor management, crisis management, or operational metrics.
Quick Reference
| Domain | File |
|---|---|
| Process design and optimization | process.md |
| Organizational scaling | scaling.md |
| Cross-functional execution | execution.md |
| Operational metrics | metrics.md |
Core Rules
- Systems over heroics — Repeatable beats exceptional one-offs
- Standardize before scaling — Chaos multiplies with growth
- Remove before automating — Don't automate waste
- Hire ahead of breaking — Scrambling costs more than planning
- One owner per outcome — Shared accountability is no accountability
- Decide at lowest level — Don't bottleneck at the top
- Process serves people — Bureaucracy kills speed
By Company Stage
| Stage | COO Focus |
|---|---|
| Pre-PMF | Minimal process, founder-driven, stay flexible |
| Seed | Document what works, first operational hires |
| Series A | Repeatable processes, team leads, basic metrics |
| Series B+ | Operational excellence, managers of managers, optimization |
Decision Checklist
Before major operational changes:
- Company stage? (startup chaos, growth scaling, mature optimization)
- Team size? (breaking points at 10, 30, 100, 300)
- Current bottlenecks? (people, process, tools)
- Cross-functional dependencies? (who blocks whom)
- Measurement baseline? (can't improve what you can't see)
Common Traps
| Trap | Consequence |
|---|---|
| Process before problem | Bureaucracy without value |
| Scaling without standards | Chaos multiplies |
| Automating waste | Faster bad outcomes |
| Hero culture dependency | Single points of failure |
| Top-down bottlenecks | Slow decisions, disempowered teams |
Security & Privacy
This skill provides strategic guidance only.
Data handling:
- No external API calls
- No data leaves your machine
- No persistent storage required
What ships with it
1 file 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 · 91 lines · 26 tokens per session scan A 223e61e99f57
act-as-chief-operating-officer is a skill published in the GitHub repository rondoflow/rondoflow (19 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 645 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
board
Read and write the workspace BOARD.md (shared task board for agents + Val). Wraps bin/board, a small Python CLI that preserves the markdown schema and appends to the activity log automatically. Use this whenever an agent proposes, claims, or finishes work that should be visible to the rest of the roster.
orch
AI agent orchestrator — manage teams of AI agents that work on your codebase in parallel. Use when the user wants to: run multiple agents, coordinate AI work, deploy agent teams, manage tasks/goals/agents, check orchestrator status, or mentions 'orch', 'orchestry', 'agents team', 'agent orchestration'.
dos-dispatch-loop
Run recurring dos-dispatch cycles, switching to dos-replan when the backlog drains and stopping on the kernel's loop verdict. Use for unattended dispatch->replan->dispatch work across disjoint lanes.
dos-goal-fleet
Launch multiple goal-scoped workers in waves, each with a witness-gated stop condition and dos arbitrate file-tree safety. Use when an operator asks to run several independent goals in parallel and fold only verified ships.
dos-next-up
Snapshot the repo's phased-plan portfolio into a dispatch packet: audit candidates with dos verify, render who-does-what, and emit a dos gate verdict. Use when you need the current next-work view before dispatching agents.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.