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-tutorial-run/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-tutorial-run)<a href="https://agentmods.dev/skills/tjmustard/hypergraph-coding-agent-framework/hyper-tutorial-run"><img src="https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-tutorial-run/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-tutorial-run"><img src="https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-tutorial-run.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.00043 | $0.00883 |
| Opus 5.5 | $0.00017 | $0.00353 |
| Sonnet 5.5 | $0.00009 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
tutorial-run 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tutorial Run
This skill reads any tutorial produced by /hyper-tutorial-generator and walks the user through it interactively — one section at a time, with in-context Q&A and on-demand access to code samples and supporting files.
When to use this skill
- When the user runs
/hyper-tutorial-runand wants to work through an existing tutorial. - When the user wants an interactive guided read (not a plain file open) of a
tutorials/<name>/folder.
How to use it
Step 0 — Choose a tutorial (HITL Gate #1)
List all subdirectories of tutorials/ (numbered). If the directory does not exist or is empty, inform the user and suggest running /hyper-tutorial-generator first.
Use AskUserQuestion to let the user select which tutorial to run. Wait for the selection before proceeding.
Step 1 — Load the tutorial
- Read
tutorials/<name>/tutorial.mdin full. - Extract the section headings to build a section list (use
##or###level headings). - Scan for available supporting subdirectories and note what's present:
code_samples/— runnable code examplesoutput_files/— expected outputsarchitecture_evolution/— diagrams and comparison tablesinput_files/— setup or example input files
- Display a brief ready message:
Ready to begin: <Tutorial Title>
Sections: N
Supporting files: code_samples/ (X files), output_files/ (Y files)
Let's start with Section 1.
Step 2 — Walk through sections (iterative HITL loop)
For each section in the tutorial:
-
Present the full section content as plain text (render markdown headers and lists).
-
Offer options via AskUserQuestion:
Section <N>/<Total>: <Section Title> Options: - Option A: Next section - Option B: I have a question about this section - Option C: Show me the code sample referenced in this sectionOnly show Option C if the section references a file in
code_samples/. -
Handle each response:
- Option A — move to the next section. If this was the last section, go to Step 3.
- Option B — answer the question using the tutorial content and your knowledge of the project. Do not move forward. Re-present the same section prompt after answering.
- Option C — identify the referenced
code_samples/file from the section text, read it in full, and display it. Then re-present the same section prompt.
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 · 102 lines · 43 tokens per session scan A bc003d113eb0
tutorial-run is a skill published in the GitHub repository tjmustard/Hypergraph-Coding-Agent-Framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 883 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
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.