A role for directing other coding agents and deciding how work is divided and executed. CEO means Chief Executive Officer, the person responsible for overall direction in a company.

Use it to design work lanes, assign tasks, monitor agent behaviour, review reports, stop work that leaves scope, and move execution between stages.

It provides central control over task assignment, decisions, progress checks, and scope changes across multiple agents.

ceo — Skill for Claude Code and Codex by tamnguyendinh

Install

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.

Any agent

npx skills add tamnguyendinh/Anvien --skill ceo

Clone the repo

git clone --depth 1 https://github.com/tamnguyendinh/Anvien

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tamnguyendinh/anvien/ceo/github.svg)](https://agentmods.dev/skills/tamnguyendinh/anvien/ceo)

Your own site

<a href="https://agentmods.dev/skills/tamnguyendinh/anvien/ceo"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/ceo/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tamnguyendinh/anvien/ceo"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/ceo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,413 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 3 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Memory Poisoning · line 42
Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.

Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
medium Agent Snooping · line 14
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
medium Agent Snooping · line 14
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00033	$0.04413
Opus 5	$0.00016	$0.02207
Sonnet 5	$0.00007	$0.00883
Haiku 4.5	$0.00003	$0.00441

Measured 3d ago against content hash 5ca212221086, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

ceo 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 3d 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.

internal/aicontext/skills/ceo/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Prompt: You are the Chief Executive Officer (CEO Agent) of the entire system, tasked with operating, supervising, and directing subagents to work.

CEO (and only CEO) use this skill.

(MUST) Your actual responsibilities are: designing lanes, assigning tasks, monitoring behaviors, blocking scope deviations, receiving verdicts, issuing executive commands, and transitioning execution steps.

Absolute Laws

There is only one valid operational mode for the CEO: direct, 100% execution of the raw rules in AGENTS.md, working-rules/SKILL.md, ceo/SKILL.md, and all files in references/. There are no summaries, alternative interpretations, or secondary "operational paraphrases".
Rule applicability check is a mandatory pre-action gate before taking any action.

Iron Rule Files (Anti-Summarization Rule)

(MUST NOT) summarize, shorten, or compact AGENTS.md, skills/ceo/SKILL.md, and skills/working-rules/SKILL.md under any circumstances.
(MUST) Read all reference files in references/ sequentially through EOF before confirming to the Owner that the CEO lane is ready for operation.
(MUST) apply 100% of the raw, unmodified rules from these three .md files at all times. Using summarized, abbreviated, or compacted versions of these rules to work is strictly forbidden in any form.
(MUST) explicitly state and mandate this absolute adherence requirement to the new CEO successor during the handoff process. The new CEO session MUST inherit and enforce this exact standard.

THE "EXECUTION-FIRST" & "ANTI-DOC-AUDIT" IRON RULE

(MUST) The Plan/Documentation defines the GOAL and the PROBLEM. The Codebase is the EXECUTION TARGET.
(MUST NOT) NEVER fall into "Document Audit Loops". When functional subagents (Coder, QA, Architect, Supervisor) read the documentation to understand the requirements, they must immediately transition their operational focus to the codebase. It is strictly forbidden to pull these functional subagents into proofreading, wording debates, or formatting audits of the documentation.
(MUST) Strictly delineate plan reading and documentation update methods to prevent loops and context bloat:
- Plan Reading Authority (Goal vs. Audit): CEO reads plan.md and SPEC files strictly to understand the problem, extract scope, and package task contracts for subagents. CEO is STRICTLY FORBIDDEN from reading documentation to proofread spelling, debate wording, or audit text structure. While a slice is running, CEO does not redundantly re-read the plan; upon completing a slice/phase, CEO reads only the updated section and next slice scope to package the next contract.
- Mechanical Status Updates (Short-Lived Planner Lane Delegation): CEO MUST NOT directly edit documentation files (plan.md, actual-status.md, evidence.md, benchmark.md) to preserve its context window. When Supervisor officially PASSes an entire Slice or Phase, CEO opens a short-lived Mechanical Planner Lane with an exact contract (specific slice/item to check/update) and a STRICT PROHIBITION against auditing, reformatting, or proofreading. Once the tick is applied, Planner Lane reports PASS and immediately closes.
- Creating Plans & Major Scope Changes: CEO opens a dedicated Planner Lane to draft or translate plans from Architect/Owner technical outcomes. Even in this mode, Planner Lane must write decisively and is strictly forbidden from falling into meaningless text-structure self-audit loops.

Read the full file on GitHub · 112 lines

Files

What ships with it

10 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.

Changes

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.

3d ago Changed · +42 lines 5ca212221086
8d ago Changed · -21 lines c62dbe0d9803
12d ago First seen · 91 lines · 33 tokens per session scan A 0b17b267041e

Subscribe to this mod's changes

ceo is a skill published in the GitHub repository tamnguyendinh/Anvien (9 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 4,413 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.

Building agents Planning ai-agents code-intelligence-mcp dead-code-detection developer-tools graph-database graph-visualization

kin-retrieval

Read a codebase through Kin's semantic graph instead of grep and whole-file reads. Use when finding where something lives, what a symbol does, who calls it, or which code implements a described behavior, and when a repo has been admitted to Kin (a .kin/ directory exists).

firelock-ai/kin · 63 tokens

blast-radius-review

Review a change by its blast radius, using Kin's graph to find what downstream code the change can reach. Use when reviewing a diff or pull request, deciding whether an edit is safe, or answering "what else breaks if I change this" in a repository admitted to Kin.

firelock-ai/kin · 60 tokens

booboo-deploy

Stand up a Booboo brain end to end — scaffold the project, write booboo.config.yaml against a real Postgres/Supabase or JSON source, build the snapshot, then wire the REST API, the MCP server, the 3D viewer and the panel. Use when someone wants a brain built for the first time, wants to point Booboo at their own…

jessymariau/booboo · 94 tokens

booboo-troubleshoot

Diagnose a Booboo brain that is not working — an empty or tiny graph, a flat starburst view, missing MCP tools, a client that cannot find the snapshot, climbing orphan counts, or a build that exits clean but produces nothing. Use when a booboo build, serve, mcp, view, panel or vault command misbehaves.

jessymariau/booboo · 79 tokens

booboo

Build, query, deploy and debug a Booboo brain — one graph fusing structure, knowledge, memory, agents and automations, queryable by REST or MCP and viewable in 3D. Use when the user mentions Booboo, booboo.config.yaml, brain.json, org.booboo.json, an organigram of agents, "boot my agent from the org", a 3D system…

jessymariau/booboo · 121 tokens

booboo-adapter

Feed data into a Booboo brain that the built-in postgres and json adapters do not cover — write a small config-driven adapter against the spec instead of forking the builder. Use when a source is Neo4j, an API, a CSV export, a proprietary store, or any shape the standard config cannot express.

jessymariau/booboo · 71 tokens