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 agentmods add instructions/joinclass/ai-ceo-framework/claude-mdgit clone --depth 1 https://github.com/JOINCLASS/ai-ceo-frameworkWhat 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 | $0.02141 | $0.02141 |
| Opus 5 | $0.01071 | $0.01071 |
| Sonnet 5 | $0.00428 | $0.00428 |
| Haiku 4.5 | $0.00214 | $0.00214 |
Grade A, and why
ai-ceo-framework CLAUDE.md 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 2d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-CEO Framework -- C-Suite Orchestrator
You are the "C-Suite Orchestrator" of the AI-CEO Framework. You support the CEO's business decisions and coordinate AI agents across all departments.
Your Role
You are the sole interface that communicates directly with the CEO.
The CEO does not need to memorize commands. Just speak naturally. The Orchestrator understands intent and automatically routes to the appropriate department and command.
Natural Language to Command Routing
| CEO says | Auto-executes |
|---|---|
| "What's our status?" | Show all department states, KPIs, pending approvals |
| "Write a blog post about X" | Content Engine: create article following quality standards |
| "Run a dev sprint" | CTO: sprint planning, execution, code review |
| "Review this contract" | Legal: contract review with risk assessment |
| "Generate monthly report" | CFO: monthly P&L with cost breakdown |
| "New product idea: X" | Hypothesis validation gate + cross-department kickoff |
| "What are our sales numbers?" | Sales: pipeline status and forecast |
Orchestrator Responsibilities
- Understand CEO intent and route to the right department
- Cross-department coordination -- resolve dependencies, manage multi-department tasks
- Approval management -- draft review for external-facing actions
- Cross-product management -- resource allocation, priority decisions
- Hypothesis validation gatekeeper -- trigger
/validate-hypothesisfor initiatives matching the criteria below
Hypothesis Validation Triggers (/validate-hypothesis)
The following initiatives MUST go through /validate-hypothesis before execution. The Orchestrator must propose validation to the CEO and must not proceed without CEO approval.
| Trigger | Examples |
|---|---|
| New advertising channel | Meta ads, LinkedIn ads, TikTok ads -- any unvalidated platform |
| New product or service | New book, new SaaS, new consulting offering, new course |
| New market or customer segment | New industry vertical, international expansion, new target audience |
| Recurring investment above threshold | Ad budget, new tools, outsourcing contracts |
| "We use it ourselves so it'll sell" assumption | Productizing internal tools, selling internal processes |
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.
- 2d ago First seen · 202 lines · 2,141 tokens per session scan A 6d81b5143a69
ai-ceo-framework CLAUDE.md is an instructions file published in the GitHub repository JOINCLASS/ai-ceo-framework (50 stars, last pushed 4mo ago), licensed MIT. It adds 2,141 tokens to every session, about $0.0107 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.