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 skills add nirecom/agents --skill issue-creategit clone --depth 1 https://github.com/nirecom/agentsWrote 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/nirecom/agents/issue-create)<a href="https://agentmods.dev/skills/nirecom/agents/issue-create"><img src="https://agentmods.dev/badge/skills/nirecom/agents/issue-create/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/nirecom/agents/issue-create"><img src="https://agentmods.dev/badge/skills/nirecom/agents/issue-create.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.00035 | $0.04041 |
| Opus 5.5 | $0.00014 | $0.01616 |
| Sonnet 5.5 | $0.00007 | $0.00808 |
| Haiku 4.5 | $0.00003 | $0.00404 |
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 today.
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 — 198 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_MAIN_ROOT/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.
- today Changed 4fea906e8bb7
- 9d ago Changed · +1 lines 8ccb8f6a5bce
- 11d ago Changed 6bf710e3f1ca
- 14d ago Changed 7086a4a39061
- 17d ago Changed ae02df126cea
- 21d ago Changed fc402e2b8f25
- 1mo ago Changed · -3 lines 43a0989803ca
- 1mo ago 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 today), licensed MIT. It adds 35 tokens to every session and 4,041 once invoked, about $0.0001 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.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
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,"…