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-create-issue/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-create-issue)<a href="https://agentmods.dev/skills/tjmustard/hypergraph-coding-agent-framework/hyper-create-issue"><img src="https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-create-issue/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-create-issue"><img src="https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-create-issue.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.00045 | $0.00707 |
| Opus 5.5 | $0.00018 | $0.00283 |
| Sonnet 5.5 | $0.00009 | $0.00141 |
| Haiku 4.5 | $0.00005 | $0.00071 |
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 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 — 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 workThen 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 urgencyFor any remaining gaps (current vs. desired behavior, specific symptoms), ask inline in the same message.
-
Search for Context
- Check
spec/compiled/architecture.ymlto identify the specificnode_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.
- Check
-
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)
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 · 68 lines · 45 tokens per session scan A 9dfb7318012c
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.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…