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-close-migratednpx skills add nirecom/agents --skill issue-close-migratedgit 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-close-migrated)<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="Measured on agentmods" 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 | $0.00035 | $0.00475 |
| Opus 5 | $0.00017 | $0.00237 |
| Sonnet 5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
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 3d 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.
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)INTOfrom the invocation arguments. - Verify issue
Nis OPEN:gh issue view N --json state --jq .state. Not OPEN → report and exit 0. - For
--type migrated: verify issueINTOis OPEN. Not OPEN → report and exit 0.
Run: bash "$AGENTS_CONFIG_DIR/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:
bash "$AGENTS_CONFIG_DIR/bin/github-issues/close-not-planned.sh" \
--type "$TYPE" $([ "$TYPE" = "migrated" ] && echo "--into $INTO") \
"$N"
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"viaclose-not-planned.sh. Never use--reason completedfor migrated or cancelled issues. - Never invoke
gh issue closedirectly from this skill — useclose-not-planned.sh.
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.
- 3d ago First seen · 40 lines · 35 tokens per session scan A 1103d010db9e
issue-close-migrated is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 475 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…