What is create-issue?

A skill for recording a bug, feature request, documentation problem, or maintenance task as a structured GitHub issue. GitHub issues are shared work items used to track software changes.

Use it to create a clear ticket while coding, including bugs to fix, features to add, documentation to improve, or technical maintenance work.

It lets you capture an idea or problem without breaking concentration during development. It also prompts for key details such as the issue type and priority.

create-issue — Skill by tjmustard

Install

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.

agentmods

npx agentmods add skills/tjmustard/hypergraph-coding-agent-framework/hyper-create-issue

Any agent

npx skills add tjmustard/Hypergraph-Coding-Agent-Framework --skill hyper-create-issue

Clone the repo

git clone --depth 1 https://github.com/tjmustard/Hypergraph-Coding-Agent-Framework

Made for: Claude Code, Codex.

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 707 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00045	$0.00707
Opus 5	$0.00023	$0.00353
Sonnet 5	$0.00009	$0.00141
Haiku 4.5	$0.00005	$0.00071

Measured yesterday against content hash 9dfb7318012c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-issue 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.

.agents/skills/hyper-create-issue/SKILL.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Issue

This skill captures a bug, feature request, or improvement as a complete, well-structured GitHub issue — fast. The user is mid-development and wants to capture an idea without losing their flow.

When to use this skill

When the user is mid-development and thinks of a bug, feature, or improvement to capture.
When the user explicitly runs /hyper-create-issue.
When the user says something like "log this as an issue" or "create a ticket for this."

How to use it

Ask Targeted Questions The user is mid-flow — be concise. Use AskUserQuestion to collect issue type and priority without multiple back-and-forths:

What type of issue is this?

- Option A: Bug — something is broken or behaving incorrectly
- Option B: Feature request — new functionality desired
- Option C: Documentation — docs are missing or incorrect
- Option D: Chore / maintenance — tech debt, refactor, or infra work

Then use AskUserQuestion for priority (if not obvious from context):

What priority should this issue have?

- Option A: Critical — blocking, needs immediate attention
- Option B: High — important, should be addressed soon
- Option C: Medium — normal backlog item
- Option D: Low — nice-to-have, no urgency

For any remaining gaps (current vs. desired behavior, specific symptoms), ask inline in the same message.

Search for Context
- Check spec/compiled/architecture.yml to identify the specific node_ids that this issue will affect.
- Search the codebase to find the relevant implementation files linked to those nodes.
- Note any risks, dependencies, or architectural constraints spotted.
Draft the Issue Create a complete issue with:
- Title: Clear, concise, action-oriented
- TL;DR: One-sentence summary
- Current State vs. Expected Outcome: What happens now vs. what should happen
- Relevant Files / Nodes: Most relevant files and node_ids from the hypergraph (max 3)
- Risk/Notes: Architectural constraints, dependencies, or risks (if applicable)
- Labels: Type (bug/feature/improvement), priority (high/normal/low), effort (small/medium/large)

Read the full file on GitHub · 68 lines

Changes

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 · 68 lines · 45 tokens per session scan A 9dfb7318012c

Subscribe to this mod's changes

create-issue is a skill published in the GitHub repository tjmustard/Hypergraph-Coding-Agent-Framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 707 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.

Debugging Planning Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

openai/codex · 114 tokens

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…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens