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/openkaiden/kaiden/create-github-issuenpx skills add openkaiden/kaiden --skill create-github-issuegit clone --depth 1 https://github.com/openkaiden/kaidenWhat 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.00093 | $0.02244 |
| Opus 5 | $0.00046 | $0.01122 |
| Sonnet 5 | $0.00019 | $0.00449 |
| Haiku 4.5 | $0.00009 | $0.00224 |
Grade A, and why
create-github-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 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Issue
Create well-structured GitHub issues from plain-language descriptions using
the gh CLI. Issues conform to the target repository's YAML form templates
and are automatically assigned to the correct project board.
This skill is repo-agnostic — it reads template metadata (projects, labels,
required fields) from the repo's .github/ISSUE_TEMPLATE/ files at
runtime rather than hardcoding them.
Prerequisites
The gh CLI must be authenticated (gh auth status). If not, prompt the
user to run gh auth login.
Input
The user provides one or more of:
- Description (required) — plain-language explanation of the bug, feature, task, or epic
- Type override (optional) — explicitly request bug, feature, task, or epic
- Repo override (optional) —
owner/repowhen not filing against the current working directory's repo - Labels (optional) — specific labels to apply
- Milestone (optional) — target milestone
- Assignees (optional) — GitHub usernames to assign
Workflow
Follow these steps in order. Do not skip any step.
Step 1: Determine the target repository
Detect the repo from the current working directory using gh repo view.
If the user specified a repo explicitly, use that instead. Confirm the
repo with the user before proceeding.
Step 2: Classify the issue type
Determine the type from context. If the user specified a type, use it. Otherwise, infer from keywords in the description:
| Type | Signal words |
|---|---|
| Bug | bug, broken, crash, error, fail, regression, wrong, not working, unexpected |
| Feature | add, support, introduce, new, would be nice, should, enhance, improve, enable |
| Task | refactor, update, migrate, rename, clean up, chore, debt, remove, upgrade |
| Epic | epic, initiative, multi-sprint, umbrella, group of features, high-level |
What ships with it
1 file 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.
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 · 240 lines · 93 tokens per session scan A 1c601f55b8a9
create-github-issue is a skill published in the GitHub repository openkaiden/kaiden (100 stars, last pushed 2d ago), licensed Apache-2.0. It adds 93 tokens to every session and 2,244 once invoked, about $0.0005 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-30.
Other skills, from other repositories
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…
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…
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…
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…
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…