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-publishnpx skills add tjmustard/Hypergraph-Coding-Agent-Framework --skill hyper-publishgit 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.00051 | $0.02571 |
| Opus 5 | $0.00026 | $0.01286 |
| Sonnet 5 | $0.00010 | $0.00514 |
| Haiku 4.5 | $0.00005 | $0.00257 |
Grade A, and why
hyper-publish 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 2d 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hyper-Publish: Commit, Push, and PR Creation
This enhanced skill automates the full git commit → push → (optional) PR creation workflow with human-in-the-loop (HITL) approval at each critical step.
Key improvements over basic git commit && git push:
- AI-proposes commit message from CHANGELOG
[Unreleased]+ git diff (no typing required) - Timestamps all file mtimes to post-session time
- Displays transparency gate before any changes
- HITL approval gates before each file modification and git command
- Optionally creates a GitHub PR with auto-drafted description
- No system-level approval prompts for git/gh commands (pre-approved via settings.json)
When to use this skill
- After a Claude Code session, when you want to commit changes with an AI-suggested message based on your CHANGELOG
- When you want to commit, push, and optionally create a PR in one unified workflow
- Whenever you run
/hyper-publish [message]or/hyper-publish --dry-run
How to use it
Step 0 — Initialize Permissions (automatic)
Run python .agents/skills/hyper-publish/scripts/setup_permissions.py to patch .claude/settings.json with pre-approved patterns for Bash(git *) and Bash(gh *). This prevents Claude Code from prompting for shell command approval on every invocation.
If settings.json is already configured, this step skips silently.
Step 1 — Parse Arguments
Read the $ARGUMENTS string.
- If it starts with
--dry-run, setDRY_RUN=trueand strip--dry-runfrom the remaining string. - If the remaining string starts with
--skip-pr, setSKIP_PR=trueand strip it. - If remaining string is non-empty, use it as
COMMIT_MESSAGE(skip Step 3 and proceed to Step 4). - If remaining string is empty, proceed to Step 3 (generate message suggestion).
Examples:
/hyper-publish→ Suggest message, offer PR/hyper-publish "Update README"→ Use provided message, offer PR/hyper-publish --dry-run→ Dry-run mode, suggest message/hyper-publish --skip-pr "Release v1.0"→ Use provided message, skip PR step
What ships with it
8 files 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.
- examples/example_commit_messages.md 3.0 KB
- examples/example_pr_description.md 2.2 KB
- META.yml 310 B
- resources/commit_template.md 1.9 KB
- resources/pr_description_template.md 1.9 KB
- scripts/generate_commit_message.py 8.2 KB runs code
- scripts/generate_pr_description.py 5.2 KB runs code
- scripts/setup_permissions.py 2.6 KB runs code
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.
- 2d ago First seen · 368 lines · 51 tokens per session scan A 4bb2bc0a3526
hyper-publish is a skill published in the GitHub repository tjmustard/Hypergraph-Coding-Agent-Framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 2,571 once invoked, about $0.0003 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
release
Create a new es-toolkit release (version bump, changelog, tag).
ship
Commit and push the current work properly — lint, run the release gate, write a detailed commit message, push to GitHub. Use whenever work reaches a milestone or the user says ship it, commit, or push.
comet-safe-delivery
在保护无关脏改动、关联 worktree、子模块和用户明确边界的前提下，提交、推送、合并或完成范围明确的 Comet 变更。用户要求提交、推送、合并回目标分支、清理 worktree 或交付已准备好的改动时使用。.