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 skills/tjmustard/hypergraph-coding-agent-framework/hyper-new-workflownpx skills add tjmustard/Hypergraph-Coding-Agent-Framework --skill hyper-new-workflowgit clone --depth 1 https://github.com/tjmustard/Hypergraph-Coding-Agent-FrameworkWhat 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.00042 | $0.00638 |
| Opus 5 | $0.00021 | $0.00319 |
| Sonnet 5 | $0.00008 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
new-workflow 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 yesterday.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Workflow
This skill converts a description of desired agent behavior into a properly formatted workflow file, making it immediately available as a slash command.
When to use this skill
- When the user asks to create a new "command" or "workflow" from an idea or prompt.
- When the user explicitly runs
/hyper-new-workflow [command_name] [description]. - After
/hyper-prompt-engineercompletes and the user chooses to export as a workflow.
How to use it
-
Gather Inputs
-
Extract the command name and its intended behavior from the user's request.
-
If only a description is provided, suggest a short, hyphen-separated name (e.g.,
code-review,api-design). -
Confirm a concise description for the frontmatter. Then use AskUserQuestion to confirm before drafting:
Confirm the command name and description? - Option A: Looks good — proceed as suggested - Option B: Change the name — specify a different name (use Other) - Option C: Change the description — modify the description (use Other)
-
-
Draft the Skill File
- Create the skill directory:
.agents/skills/<command-name>/ - Create the main file:
.agents/skills/<command-name>/SKILL.md - Mandatory frontmatter — start the file with:
--- name: <command-name> description: <concise third-person description of what this skill does> trigger: /<command-name> --- - Structure the content using the standard skill format:
## When to use this skill— trigger conditions## How to use it— numbered steps for the agent to follow. Be explicit about agent actions, not just outcomes.
- Create the skill directory:
-
Create IDE Bridge Files
- Create a thin bridge in
.claude/commands/<command-name>.md:--- description: "<description matching SKILL.md>" --- Read `.agents/skills/<command-name>/SKILL.md` and follow its instructions precisely. - Create a thin bridge in
.windsurf/workflows/<command-name>.md:--- description: "<description matching SKILL.md>" --- Read `.agents/skills/<command-name>/SKILL.md` and follow its instructions precisely.
- Create a thin bridge in
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.
- yesterday First seen · 65 lines · 42 tokens per session scan A a9b8e7b87fe0
new-workflow is a skill published in the GitHub repository tjmustard/Hypergraph-Coding-Agent-Framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 638 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 skills, from other repositories
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…