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-process-document/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-process-document)<a href="https://agentmods.dev/skills/tjmustard/hypergraph-coding-agent-framework/hyper-process-document"><img src="https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-process-document/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-process-document"><img src="https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-process-document.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.00040 | $0.01351 |
| Opus 5.5 | $0.00016 | $0.00540 |
| Sonnet 5.5 | $0.00008 | $0.00270 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
process-document 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hyper-Process-Document
Write a process document that captures the how of this session — the problem, approach, decisions, and steps taken — so that someone reading it cold can understand and reproduce the results.
This is distinct from /hyper-handoff, which is forward-looking (context for a new agent to continue). This document is retrospective and human-readable: institutional knowledge capture.
Step 1 — Determine Output Path
Create the output directory if it does not exist:
mkdir -p spec/process
Name the file: process_<YYYYMMDD>_<slug>.md
- Use the current date for
<YYYYMMDD>(date only — no time component) - Derive
<slug>from$ARGUMENTSby lowercasing and replacing spaces/special characters with hyphens (e.g., "Dynamic Workflow Engine" →dynamic-workflow-engine) - If no
$ARGUMENTSprovided, usesessionas the slug
Disambiguate same-day documents with a version suffix. If a file with that exact name already exists (e.g. more than one process document is written on the same date), append _v2, _v3, … to the end of the filename — before the .md extension — using the next unused number. The first document of the day carries no suffix:
base="spec/process/process_$(date +%Y%m%d)_<slug>" # substitute the real <slug>
path="${base}.md"
n=2
while [ -e "$path" ]; do
path="${base}_v${n}.md"
n=$((n + 1))
done
# $path is now collision-free, e.g.
# spec/process/process_20260616_dynamic-workflow-engine.md (first of the day)
# spec/process/process_20260616_dynamic-workflow-engine_v2.md (second of the day)
Step 2 — Gather Context
Before writing, read and recall the following to reconstruct an accurate picture:
git log --oneline -20
git diff HEAD~5..HEAD --name-only
- Read
.agents/memory/activeContext.md— current sprint state and recent decisions - List
spec/active/— any in-progress PRDs or artifacts touched this session - Recall the conversation: what problems were raised, what approaches were tried, what choices were made and why
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 · 165 lines · 40 tokens per session scan A d099b45c3226
process-document is a skill published in the GitHub repository tjmustard/Hypergraph-Coding-Agent-Framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,351 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…