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-tutorial-generatornpx skills add tjmustard/Hypergraph-Coding-Agent-Framework --skill hyper-tutorial-generatorgit 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.00038 | $0.01736 |
| Opus 5 | $0.00019 | $0.00868 |
| Sonnet 5 | $0.00008 | $0.00347 |
| Haiku 4.5 | $0.00004 | $0.00174 |
Grade A, and why
tutorial-generator 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tutorial Generator
This skill converts an existing integration test or a set of user-provided files into a polished, step-by-step markdown tutorial. The process is collaborative and interactive — you and the LLM work together to draft and refine each section.
When to use this skill
- After creating an integration test, when you want to document the workflow it demonstrates as a user-facing tutorial.
- When you have example files, screenshots, or code samples that illustrate a framework feature and want to organize them into a structured tutorial.
- When you want to create educational content that walks users through a specific task or workflow.
- Whenever you run
/hyper-tutorial-generator.
How to use it
Step 0 — Choose Your Source (HITL Gate #1)
Use AskUserQuestion to ask the user which source to use:
Option A: Existing Integration Test
- Tutorial will be based on a test file from
tests/integration/ - You'll select which test and describe what aspects to focus on
Option B: User-Provided Files
- Tutorial will be built from files you provide (code, examples, docs, etc.)
- You'll describe the topic and list any supporting files
Wait for the user's selection before proceeding.
Step 1 — Gather Source Material
If Integration Test Mode:
- List all files in
tests/integration/(numbered). - Use AskUserQuestion to let the user select which test file to use.
- Read the selected test file in full.
- Then ask via AskUserQuestion: "What aspects of this test should the tutorial focus on? (e.g., the core workflow, specific edge cases, debugging tips)"
- Wait for the response.
If User Files Mode:
- Use AskUserQuestion (two parts):
- "What is this tutorial about? (1-2 sentences)"
- "Do you have any input files, code samples, examples, or screenshots to include? If yes, list their file paths or paste their content directly."
- For any listed files, read them in full (or accept pasted content).
- Store all provided content in memory for use in later steps.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 195 lines · 38 tokens per session scan A 8597160a0cc7
tutorial-generator is a skill published in the GitHub repository tjmustard/Hypergraph-Coding-Agent-Framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,736 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
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
a-evolve
Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后,主动执行此流程! 将学到的经验归档为 skill,供以后参考。不要等用户提醒。.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.