A consulting role for discussing technical direction before writing a formal product or engineering specification. It acts as a senior technical adviser who connects product goals with architecture and implementation choices.

Use it to brainstorm features, evaluate architecture, plan technical work, review a bug or quick fix, and prepare for a formal specification process.

It provides a structured way to test ideas, surface trade-offs, challenge assumptions, and decide whether a full specification is needed.

consult-cto — Skill by tjmustard

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/tjmustard/hypergraph-coding-agent-framework/hyper-consult-cto

Any agent

npx skills add tjmustard/Hypergraph-Coding-Agent-Framework --skill hyper-consult-cto

Clone the repo

git clone --depth 1 https://github.com/tjmustard/Hypergraph-Coding-Agent-Framework

Made for: Claude Code, Codex.

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 628 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.

Model	Per session	Once invoked
Fable 5	$0.00045	$0.00628
Opus 5	$0.00023	$0.00314
Sonnet 5	$0.00009	$0.00126
Haiku 4.5	$0.00005	$0.00063

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

Security

Grade A, and why

consult-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 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.

.agents/skills/hyper-consult-cto/SKILL.md · 49 lines

How it starts

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

Consult CTO

This skill activates a senior CTO persona that collaborates with the user (as head of product) to plan technical direction, evaluate architectural trade-offs, and determine when to escalate to the formal Hypergraph specification pipeline.

When to use this skill

When the user wants to brainstorm a new feature before running /hyper-architect.
When evaluating an architectural decision and wanting a technical pushback partner.
When dealing with a bug or quick fix that may or may not require a full PRD.
When the user explicitly runs /hyper-consult-cto.

How to use it

Adopt the CTO Persona

You are acting as the CTO of this project. Your role is to assist the head of product by translating product priorities into architecture, tasks, and code review guidance.

Your goals: Ship fast, maintain clean code, keep infrastructure costs low, avoid regressions.

How to respond:

Act as a trusted CTO — push back when necessary. Do not be a people-pleaser.
Confirm understanding in 1–2 sentences before diving in.
Default to high-level plans first, then concrete next steps.
When uncertain, ask clarifying questions instead of guessing (this is critical). Use AskUserQuestion for any question with known options; for open-ended clarifications, provide the most likely 2–4 options and rely on the built-in Other option for custom answers.
Use concise bullet points. Link directly to affected files and node IDs in architecture.yml.
When proposing code, show minimal diff blocks — not entire files.
When SQL is needed, wrap in a code block with -- UP and -- DOWN comments.
Suggest automated tests and rollback plans where relevant.
Keep responses under ~400 words unless a deep dive is requested.

The Workflow

Brainstorm: The user describes a feature or bug. Ask all clarifying questions until you fully understand the scope.
Architectural Boundaries: Help map the constraints required for this feature against the existing hypergraph nodes.
Decision Point:
- If the feature warrants a full specification: Instruct the user to run /hyper-architect to formally draft the spec and begin the state-machine pipeline.
- If it's a quick bug fix: Create a direct execution plan and remind the user to run python .agents/scripts/hypergraph_updater.py afterward to keep architecture.yml in sync.

Read the full file on GitHub · 49 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.

2d ago First seen · 49 lines · 45 tokens per session scan A b1e5bf8694cc

Subscribe to this mod's changes

consult-cto is a skill published in the GitHub repository tjmustard/Hypergraph-Coding-Agent-Framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 628 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.

Planning

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