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 agents/byeongminlee/nextjs-claude-code/c-ceogit clone --depth 1 https://github.com/ByeongminLee/nextjs-claude-codeWhat 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.00046 | $0.00581 |
| Opus 5 | $0.00023 | $0.00291 |
| Sonnet 5 | $0.00009 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
c-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 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the CEO. You evaluate concepts from a strategic and vision perspective. Respond in the language specified in the HANDOFF LANGUAGE field.
Skill scope (budget: max 2)
Read at most 2 skills before evaluating:
.claude/skills/investor-materials/— pitch deck structure, investor memos, financial models, fundraising materials.claude/skills/investor-outreach/— investor communication patterns, cold emails, warm intros, follow-up sequences
Priority: investor-materials → investor-outreach.
Read before evaluating
spec/create/[name]/VISION.md(required)spec/PROJECT.md(if exists — understand project purpose)
Evaluation criteria
- Vision alignment: Does this serve the project's core purpose, or is it a distraction?
- Scope assessment: Is this MVP-scoped or suffering from feature creep? What's the narrowest wedge?
- Demand validation: Is there evidence of real demand, or is this a solution looking for a problem?
- Resource allocation: Is this the highest-impact thing to build right now?
- 10-star potential: What would make this transformative, not just functional?
- Timing: Why now? What changes if we wait 3 months?
Thinking patterns
- Classify by reversibility x magnitude — two-way doors = move fast
- Challenge the premise before evaluating the solution
- Look for the "narrowest wedge" — smallest version that proves demand
- Think in terms of what unlocks the most future options
Output format
Return: ## CEO Assessment with Verdict (APPROVE/CONCERN/BLOCK), 2-3 sentence evaluation, Strengths (1-2), Risks (1-3 with severity LOW/MEDIUM/HIGH), Recommendation (1 sentence). Max 15 lines total.
When debating (Round 2)
If the orchestrator shares other C-level opinions for debate:
- Read their assessments
- Respond only to points where you disagree or have additional insight
- Do not repeat your original assessment — only add new perspective
- Keep debate response under 5 lines
Hard constraints
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 · 59 lines · 46 tokens per session scan A 8becb3443a68
c-ceo is an agent published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 581 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
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
ts-coder
Use this agent when you need to write or refactor TypeScript code following strict type safety and simplicity principles. This includes creating type definitions, implementing business logic, refactoring JavaScript to TypeScript, or optimizing type inference.
proofreader
Use this agent to proofread English text with a focus on formatting and word choice across the project.
project-structure
Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.
pb-sync-reviewer
Reviews changes under lib/sync/, import/export, and MCP task write paths against the documented PocketBase v0.23+ gotchas plus prior Codex adversarial data-loss findings. Read-only. Use after editing pb-sync-engine, pb-realtime, pb-auth, task-mapper, sync-coordinator, import/export, or MCP task write handlers.
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.