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-stagenpx skills add nirecom/agents --skill issue-close-stagegit 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-stage)<a href="https://agentmods.dev/skills/nirecom/agents/issue-close-stage"><img src="https://agentmods.dev/badge/skills/nirecom/agents/issue-close-stage.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.00044 | $0.00816 |
| Opus 5 | $0.00022 | $0.00408 |
| Sonnet 5 | $0.00009 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
issue-close-stage 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage routes to the correct subset of steps; each step is idempotent and resumable.
Read rules/github-issues.md first — on-demand-only, never auto-injected; its "Session model" defines the per-session N relation.
Read rules/coding.md before the first gh issue comment or body update — on-demand-only, never auto-injected; its Public GitHub Rules govern that outbound text.
Usage: /issue-close-stage <N> or /issue-close-stage --from-session
--from-session resolves <N> from the current session's intent.md the same
way as /issue-close-finalize: parse ## Issues and iterate.
(canonical parser: hooks/lib/parse-closes-issues.js — do not reimplement.)
Pre-flight
Run: "$AGENTS_CONFIG_DIR/bin/detect-non-github.sh" "issue-close-stage" || exit 0
On non-GitHub remote the script exits 1, so || exit 0 terminates the skill immediately (no gh work). On a GitHub remote (or unknown/fail-open) the script exits 0 and the skill continues into the checks below.
Skip message on non-GitHub remote (emitted by the script to stdout): [GITHUB_ISSUES disabled: non-GitHub remote detected, skipping issue-close-stage]
AGENTS_CONFIG_DIRmust be set.- Must be invoked from a linked worktree (not the main worktree). Abort
with an error when
git rev-parse --git-direqualsgit rev-parse --git-common-dir. - Resolve
<owner/repo>viagh repo view --json owner,name --jq '.owner.login + "/" + .name'. - All
gh issue commentinvocations needISSUE_CLOSE_SKILL=1to bypass theenforce-issue-close.jshook.
Delegation
Dispatch Steps A, B, D, F, G to the issue-close-stage worker per skills/_shared/worker-dispatch.md.
Payload keys: issue_number (= N), worktree_path (= git rev-parse --show-toplevel), owner_repo, agents_config_dir (= AGENTS_CONFIG_DIR), artifact_dir (= PLANS_DIR), issue_repo.
Omit issue_repo for current-repo issues; otherwise take it from the closes_issues entry's repo field.
Cross-repo Phase 1 is unsupported: an issue_repo naming any repo other than owner_repo is refused with error. Run /issue-close-stage from a worktree of that repository instead.
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 · 63 lines · 44 tokens per session scan A 8c0329ff4361
issue-close-stage is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 816 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…