om-cto

om-cto is a skill for Claude Code from SHGrowth/om-superpowers. It costs 76 tokens per session (1,150 once invoked), scanned A, original, MIT.

Een architectuurhulpmiddel voor Open Mercato dat onderzoekt wat het platform al kan en waar hiaten of risico’s zitten. Het ondersteunt losse adviezen, analyse van meerdere documenten, het uitschrijven van specificaties en het voorbereiden of aansturen van implementatie.

In plain words
What is it for?
Voor vragen over platformmogelijkheden, gap analysis van klantdocumenten, analyse van bounded contexts (afgebakende bedrijfsgebieden), review van skills, specificatie-opbouw en implementatieplanning. De invoer beschrijft zowel advies- als orkestratiemodi.
Why use it?
Het helpt voorkomen dat teams bestaande mogelijkheden over het hoofd zien of te vroeg een verkeerde technische oplossing kiezen. Het maakt ook afhankelijkheden tussen bedrijfsprocessen, risico’s en benodigde werkzaamheden zichtbaar.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the om-superpowers plugin — 11 skills, 1 hook shipped together

Good fit Voor vragen over platformmogelijkheden, gap analysis van klantdocumenten, analyse van bounded contexts (afgebakende bedrijfsgebieden), review van skills, specificatie-opbouw en implementatieplanning. De invoer beschrijft zowel advies- als orkestratiemodi.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/shgrowth/om-superpowers/om-cto
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 SHGrowth/om-superpowers --skill om-cto
Clone the repo
git clone --depth 1 https://github.com/SHGrowth/om-superpowers

Made for: Claude Code.

Or install om-superpowers, the plugin that ships this one along with the rest of its 11 skills, 1 hook.

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 om-cto

README.md
[![agentmods](https://agentmods.dev/badge/skills/shgrowth/om-superpowers/om-cto/github.svg)](https://agentmods.dev/skills/shgrowth/om-superpowers/om-cto)
Your own site
<a href="https://agentmods.dev/skills/shgrowth/om-superpowers/om-cto"><img src="https://agentmods.dev/badge/skills/shgrowth/om-superpowers/om-cto/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.

agentmods 80×15 button for om-cto

Your own site · 80×15
<a href="https://agentmods.dev/skills/shgrowth/om-superpowers/om-cto"><img src="https://agentmods.dev/badge/skills/shgrowth/om-superpowers/om-cto.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,150 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.
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.1 $0.00076 $0.01150
Opus 5 $0.00038 $0.00575
Sonnet 5 $0.00015 $0.00230
Haiku 4.5 $0.00008 $0.00115

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

Security

Grade A, and why

om-cto 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 9d 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/om-cto/SKILL.md · 74 lines

How it starts

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

om-cto

Architecture and gap-analysis skill for Open Mercato. Four modes: Advisory (single question about platform), Batch Gap Analysis (a folder of client docs → persisted Epic/Story backlog), Spec Orchestrator (App Spec → functional specs), Implementation Orchestrator (approved specs → code).

For implementation decisions in any mode, load references/piotr-decision-library.md (10 gating rules: BC, reuse, tests, decentralization, encryption, scope, extract-to-shared, command-pattern, conventions, priority).

Task Router

Load only the reference you need. Never load all at once.

Task Load
Gap analysis, "does OM do X?", PR review, standalone questions references/advisory.md
Multi-document engagement scoping (folder of transcripts/specs → epic/story backlog) references/gap-analysis-batch.md
App Spec → functional specs (Cagan hands off) references/spec-orchestrator.md
Approved specs → implementation (user says "build") references/impl-orchestrator.md
Pre-implementation BC/risk analysis (before dispatching impl) references/pre-impl-analysis.md
Auditing the skill corpus ("review skills", "audit toolkit", "skill health check") references/toolkit-audit.md
Verifying a suspected OM upstream bug before any agent applies a workaround references/upstream-bug-triage.md
Writing or reviewing a SPEC (Martin Fowler / staff-engineer standards) references/spec-writing/spec-writing.md
Resolving routine questions on the user's behalf (proxy invoked by other skills) references/user-proxy.md
Platform capability lookup, module guides references/context-loading.md
Gap estimation in atomic commits references/atomic-commits.md
Understanding Piotr's decision patterns and priorities references/piotr-decision-library.md

Mode Detection

  1. If an App Spec document was just completed by Cagan (om-product-manager) → Spec Orchestrator
  2. If the user references approved specs and says "build", "implement", "start", "go" → Implementation Orchestrator
  3. If the user points at a directory of client docs (transcripts/specs) or an existing gap-analysis/<project>.md and asks what to build vs. what OM already provides → Batch Gap Analysis (references/gap-analysis-batch.md)
  4. Everything else (a single capability question) → Advisory

Read the full file on GitHub · 74 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. 9d ago First seen · 74 lines · 76 tokens per session scan A 9a152fd2596f

Subscribe to this mod's changes

om-cto is a skill published in the GitHub repository SHGrowth/om-superpowers (6 stars, last pushed 6d ago), licensed MIT. It adds 76 tokens to every session and 1,150 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-31.

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

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens