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/nirecom/agents/issue-createnpx skills add nirecom/agents --skill issue-creategit clone --depth 1 https://github.com/nirecom/agentsWhat 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.00035 | $0.03996 |
| Opus 5 | $0.00017 | $0.01998 |
| Sonnet 5 | $0.00007 | $0.00799 |
| Haiku 4.5 | $0.00003 | $0.00400 |
Grade A, and why
issue-create 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.
How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The sanctioned path for creating task issues (type:task) from a Claude Code
session. Surveys existing issues first, classifies the relationship semantically,
then dispatches to a wrapper that handles reopen / sub-issue attach / new-parent
reclassification / sibling cross-reference / plain creation. The dispatcher
delegates new-issue creation to bin/github-issues/issue-create.sh.
Scope
- In scope: task issues (
type:task) for the current repository. - Out of scope: incident issues (use the web UI incident template or a
--label "type:incident"invocation of your own); issues for other repos or projects, which take the cross-repo path below. - Cross-repo work: confirm the ownership of the target repository before filing the issue — an issue lands publicly in whichever repo
ghresolves, and that resolution follows the working directory when no target is named.
Required reading: Read rules/github-issues.md before Pre-flight — it is on-demand-only and never auto-injected.
Read rules/coding.md before writing any issue title or body — on-demand-only, never auto-injected; its Public GitHub Rules govern this outbound write.
Phase 0b — Project preflight
Runs before Pre-flight. Detects a missing Projects v2 board and offers to run /issue-setup. Independent of Phase 0a (label auto-repair in issue-create.sh) — one's result never affects the other.
- Skip Phase 0b and proceed to Pre-flight when
bin/is-github-dotcom-remotereturns non-zero (non-GitHub remote). - Run
bash "$AGENTS_CONFIG_DIR/bin/github-issues/issue-create-preflight.sh" --check-project(add--repo OWNER/REPOwhen targeting another repo). - On rc=1 (no board), AskUserQuestion:
run-issue-setup: run/issue-setupagainst the target repo, then re-check Phase 0b.skip-this-time: proceed to Pre-flight; the attach step remains warn-only.
skip-this-timeis NOT persisted — Phase 0b re-checks on everyissue-createrun (no suppression state file).
Pre-flight
What ships with it
4 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.
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 · 200 lines · 35 tokens per session scan A 4c80b9cbe2a4
issue-create is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 3,996 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.
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…