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 swyxio/skills --skill ceo-creatorgit clone --depth 1 https://github.com/swyxio/skillsWrote 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/swyxio/skills/ceo-creator)<a href="https://agentmods.dev/skills/swyxio/skills/ceo-creator"><img src="https://agentmods.dev/badge/skills/swyxio/skills/ceo-creator/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/swyxio/skills/ceo-creator"><img src="https://agentmods.dev/badge/skills/swyxio/skills/ceo-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 20 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00089 | $0.01961 |
| Opus 5 | $0.00044 | $0.00981 |
| Sonnet 5 | $0.00018 | $0.00392 |
| Haiku 4.5 | $0.00009 | $0.00196 |
Grade A, and why
ceo-creator 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 10d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CEO Creator
Create a durable operating agent, not a role-play persona or a long generic prompt. Give the CEO enough initiative to discover and improve the project continuously while keeping consequential actions inside explicit authority boundaries.
Discover the project first
Inspect what is available before asking questions or changing state:
- Resolve the project, repositories, product surfaces, deployment environments, and current stage.
- Read repository instructions, status, roadmap material, product documentation, and release notes.
- Inventory active project threads, tasks, worktrees, automations, release owners, and known commitments when those sources are accessible.
- Locate analytics, signup and activation data, rate limits, error and performance telemetry, support signals, and public user-facing surfaces.
- Perform an informal visual walkthrough of the rendered product when possible. Use visual judgment to discover unbounded issues; use scripted tests later to preserve known behavior.
- Distinguish verified facts, reasonable inferences, and unknowns.
- Do not ask the user for facts that can be discovered safely from local or connected sources.
Keep discovery read-only until authority is aligned. Preserve dirty work and do not disrupt active tasks.
Align once on material choices
Use a single compact decision round for choices that materially change the CEO's behavior. Present 2–10 numbered decisions, each with mutually exclusive options, a concrete tradeoff, and a recommendation. Let the user answer tersely or approve all recommendations.
Cover only choices that remain unresolved, usually:
- Project stage and north-star outcome.
- Authority level: advisory, local operator, or full operator within named systems.
- Production and analytics visibility.
- Reporting and review cadence.
- Informal playthrough frequency and target personas.
- Delegation and concurrent-task budget.
- Privacy, external communication, spending, and release boundaries.
- Reporting form: concise brief, interactive visual pulse, or both.
- Whether to establish a dedicated CEO thread or operate in the current one.
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.
- 10d ago First seen · 184 lines · 89 tokens per session scan A 74bdb21f992c
ceo-creator is a skill published in the GitHub repository swyxio/skills (158 stars, last pushed 2d ago), licensed MIT. It adds 89 tokens to every session and 1,961 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…