ceos-ids

ceos-ids is a skill for Claude Code, Codex from bradfeld/ceos. It costs 19 tokens per session (2,508 once invoked), scanned A, original, MIT.

A structured issue-solving process from the Entrepreneurial Operating System, or EOS, called Identify, Discuss, Solve (IDS). It requires finding a root cause, discussing it, and assigning a concrete follow-up task.

In plain words
What is it for?
Use it to record open issues, work through them systematically, assign next steps, and mark solved issues in a CEOS repository.
Why use it?
It prevents team issues from remaining vague or being discussed repeatedly without a decision, owner, or due date.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/bradfeld/ceos/ceos-ids
Any agent
npx skills add bradfeld/ceos --skill ceos-ids
Clone the repo
git clone --depth 1 https://github.com/bradfeld/ceos

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.

agentmods badge for ceos-ids

README.md
[![agentmods](https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-ids.svg)](https://agentmods.dev/skills/bradfeld/ceos/ceos-ids)
Your own site
<a href="https://agentmods.dev/skills/bradfeld/ceos/ceos-ids"><img src="https://agentmods.dev/badge/skills/bradfeld/ceos/ceos-ids.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,508 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.02508
Opus 5 $0.00010 $0.01254
Sonnet 5 $0.00004 $0.00502
Haiku 4.5 $0.00002 $0.00251

Measured 4d ago against content hash fb91c1b84296, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ceos-ids 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 4d 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.

skills/ceos-ids/SKILL.md · 263 lines

How it starts

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

ceos-ids

Run the IDS (Identify, Discuss, Solve) process — the EOS method for resolving issues systematically. Every issue gets a root cause, a focused discussion, and at least one To-Do with an owner and due date.

When to Use

  • "We have an issue" or "add to the issues list"
  • "IDS this" or "let's identify discuss solve"
  • "What are our open issues?" or "show the issues list"
  • "Solve [issue]" or "discuss [issue]"
  • "Close this issue" or "mark [issue] as solved"
  • During L10 meetings when the IDS section begins
  • Any time the team needs structured problem-solving

Context

Finding the CEOS Repository

Search upward from the current directory for the .ceos marker file. This file marks the root of the CEOS repository.

If .ceos is not found, stop and tell the user: "Not in a CEOS repository. Clone your CEOS repo and run setup.sh first."

Sync before use: Once you find the CEOS root, run git -C <ceos_root> pull --ff-only --quiet 2>/dev/null to get the latest data from teammates. If it fails (conflict or offline), continue silently with local data.

Key Files

File Purpose
data/issues/open/ Open issues awaiting resolution
data/issues/solved/ Resolved issues (archive)
templates/issue.md Template for new issue files

Issue File Format

Each issue is a markdown file with YAML frontmatter:

id: issue-001
title: "Slow customer onboarding"
priority: 1            # 1 (highest) - 5 (lowest)
category: process      # people | process | data | vision | traction
ids_stage: identified  # identified | discussed | solved
created: "2026-02-06"

Priority levels:

  • 1 — Critical, solve first
  • 2 — High, solve soon
  • 3 — Medium, solve when time allows
  • 4 — Low, solve if capacity allows
  • 5 — Nice-to-have, backlog

Categories (the 5 EOS issue types):

  • people — right person, right seat issues
  • process — systems, workflows, efficiency
  • data — metrics, reporting, information gaps
  • vision — alignment with V/TO, Core Focus
  • traction — execution, accountability, follow-through

Read the full file on GitHub · 263 lines

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.

  1. 4d ago First seen · 263 lines · 19 tokens per session scan A fb91c1b84296

Subscribe to this mod's changes

ceos-ids is a skill published in the GitHub repository bradfeld/ceos (145 stars, last pushed 25d ago), licensed MIT. It adds 19 tokens to every session and 2,508 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens