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-template-architectnpx skills add tjmustard/Hypergraph-Coding-Agent-Framework --skill hyper-template-architectgit 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.00041 | $0.00686 |
| Opus 5 | $0.00020 | $0.00343 |
| Sonnet 5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
template-architect 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Template Architect
This skill assumes the role of an expert Template Architect. Given a filled-out source document, it reverse-engineers a reusable Markdown template with precise, actionable instructional placeholders — designed for a downstream AI agent to fill in.
When to use this skill
- When the user provides a completed document and asks for a reusable template.
- When the user explicitly runs
/hyper-template-architect. - When a one-off document needs to be converted into a repeatable pattern.
How to use it
-
Wait for Input If the user did not provide a source document with the command, use AskUserQuestion:
How would you like to provide the source document? - Option A: I'll paste the content — type or paste the document directly - Option B: It's already in a file — provide the file path and I will read itDo not proceed without the document.
-
Apply the Transformation Rules
- Header Fidelity: Retain all headers exactly as they appear in the source text (unless the user explicitly asked to generalize them).
- Instructional Placeholders: Remove all specific details, proper nouns, and data. Replace with square-bracketed directives. The text inside brackets MUST be a clear, actionable instruction for the downstream agent — not a generic label.
- ✅
[Extract the primary technical limitation described in the source text] - ❌
[Problem]
- ✅
- List Generalization: Do not hardcode the number of list items. Create a pattern for one item and add an instruction to repeat it (e.g.,
*(Repeat this format for all relevant items...)*). - Citation Stripping: Completely remove citation markers (e.g.,
[001],(Smith, 2024)). Do not create placeholders for them. - Formatting Preservation: Preserve all Markdown syntax (bolding, italics, spacing, structural hierarchy) from the original.
-
Anti-Overwrite Check Before finalizing a filename, check the
.agents/schemas/directory. If the intended filename already exists, append a version number (e.g.,api-integration-template-v2.md).
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 · 54 lines · 41 tokens per session scan A 254a2d43c1bd
template-architect is a skill published in the GitHub repository tjmustard/Hypergraph-Coding-Agent-Framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 686 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…