What is issue-close-migrated?

A workflow step for closing an issue because it was merged into another issue or is no longer planned. It applies the relevant status and comment before closing it.

Use it to mark an issue as migrated into another open issue or cancel it as not planned, with the required checks and labels.

It keeps the issue tracker accurate when work has moved elsewhere or has been cancelled.

issue-close-migrated — Skill for Claude Code by nirecom/agents

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.

Any agent

npx skills add nirecom/agents --skill issue-close-migrated

Clone the repo

git clone --depth 1 https://github.com/nirecom/agents

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nirecom/agents/issue-close-migrated/github.svg)](https://agentmods.dev/skills/nirecom/agents/issue-close-migrated)

Your own site

<a href="https://agentmods.dev/skills/nirecom/agents/issue-close-migrated"><img src="https://agentmods.dev/badge/skills/nirecom/agents/issue-close-migrated/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nirecom/agents/issue-close-migrated"><img src="https://agentmods.dev/badge/skills/nirecom/agents/issue-close-migrated.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00035	$0.00493
Opus 5.5	$0.00014	$0.00197
Sonnet 5.5	$0.00007	$0.00099
Haiku 4.5	$0.00003	$0.00049

Measured 11d ago against content hash 3a933b81f8d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

issue-close-migrated 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 11d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/pre-flight.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/issue-close-migrated/SKILL.md · 36 lines

What it actually says

Close issue <N> as migrated (merged into another issue) or cancelled.

Usage:

/issue-close-migrated <N> --type migrated --into <M> — issue N merged into M
/issue-close-migrated <N> --type cancelled — issue N cancelled

--into <M> is required for --type migrated and prohibited for --type cancelled.

Pre-flight

Read rules/github-issues.md first — on-demand-only, never auto-injected.

Parse N, TYPE, and (if migrated) INTO from the invocation arguments.
Verify issue N is OPEN: gh issue view N --json state --jq .state. Not OPEN → report and exit 0.
For --type migrated: verify issue INTO is OPEN. Not OPEN → report and exit 0.

Run: bash "$AGENTS_MAIN_ROOT/skills/issue-close-migrated/scripts/pre-flight.sh" "$N" "$TYPE" "$INTO" || { echo "Pre-flight failed — check issue state"; exit 0; }

Procedure

Run bin/github-issues/close-not-planned.sh as one standalone call: bash "$AGENTS_MAIN_ROOT/bin/github-issues/close-not-planned.sh" --type "<TYPE>" "<N>". Only when <TYPE> is migrated, write --into <INTO> into the argument list yourself, before <N> — do not build that argument with a shell conditional.

The gh issue close inside close-not-planned.sh is a subprocess of the Bash tool command — enforce-issue-close.js (PreToolUse) fires only on the Bash tool command head, not on subprocess calls. No bypass marker is required.

Rules

Always close with --reason "not planned" via close-not-planned.sh. Never use --reason completed for migrated or cancelled issues.
Never invoke gh issue close directly from this skill — use close-not-planned.sh.

Files

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.

scripts/pre-flight.sh 829 B runs code

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.

11d ago Changed 3a933b81f8d3
1mo ago Changed · -4 lines 5e870fe22504
1mo ago First seen · 40 lines · 35 tokens per session scan A 1103d010db9e

Subscribe to this mod's changes

issue-close-migrated 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 493 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.

Project management

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.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

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,"…

petrkindlmann/qa-skills · 124 tokens