Borrowing it
Nothing to install: this file belongs to tjmustard/Hypergraph-Coding-Agent-Framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tjmustard/Hypergraph-Coding-Agent-Framework/main/.agents/skills/hyper-consult-cto/SKILL.mdgit clone --depth 1 https://github.com/tjmustard/Hypergraph-Coding-Agent-FrameworkWrote 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/tjmustard/hypergraph-coding-agent-framework/hyper-consult-cto)<a href="https://agentmods.dev/skills/tjmustard/hypergraph-coding-agent-framework/hyper-consult-cto"><img src="https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-consult-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.
<a href="https://agentmods.dev/skills/tjmustard/hypergraph-coding-agent-framework/hyper-consult-cto"><img src="https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-consult-cto.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00045 | $0.00628 |
| Opus 5.5 | $0.00018 | $0.00251 |
| Sonnet 5.5 | $0.00009 | $0.00126 |
| Haiku 4.5 | $0.00005 | $0.00063 |
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 2mo 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 — 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
-- UPand-- DOWNcomments. - 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-architectto 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.pyafterward to keeparchitecture.ymlin sync.
- If the feature warrants a full specification: Instruct the user to run
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.
- 2mo ago First seen · 49 lines · 45 tokens per session scan A b1e5bf8694cc
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.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 skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…