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-close-finalizegit 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-finalize)<a href="https://agentmods.dev/skills/nirecom/agents/issue-close-finalize"><img src="https://agentmods.dev/badge/skills/nirecom/agents/issue-close-finalize/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-close-finalize"><img src="https://agentmods.dev/badge/skills/nirecom/agents/issue-close-finalize.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.00073 | $0.02910 |
| Opus 5.5 | $0.00029 | $0.01164 |
| Sonnet 5.5 | $0.00015 | $0.00582 |
| Haiku 4.5 | $0.00007 | $0.00291 |
Grade A, and why
issue-close-finalize 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage routes to the correct subset of in-skill steps; each is idempotent and resumable. Read rules/github-issues.md first — on-demand-only, never auto-injected; its "Session model" defines per-session N. Usage: /issue-close-finalize <N> or /issue-close-finalize --from-session.
Read rules/coding.md before the first close comment or parent-body update — on-demand-only, never auto-injected; its Public GitHub Rules govern that outbound text.
--from-session resolves <N> from node "$AGENTS_MAIN_ROOT/bin/parse-closes-issues" --session <session-id> (the session's owner-resolved intent ## Issues). Zero → skip; one → continue; multiple → run sequentially; missing intent → one-line warn + skip. The merge commit is resolved from the PR in ICF-B, not from a flag.
--from-session per-N dispatch obligations
Enumerate every N in closes_issues via parse-closes-issues.js — the ## Issues block lists all values, including subsumed siblings. For each N in insertion order:
- Open sub-issue gate (#417): before dispatching the pipeline, if the issue is OPEN, run
bash "$AGENTS_MAIN_ROOT/bin/github-issues/parent-all-closed-check.sh" "<OWNER_REPO>" <N>. On exit 1 (open sub-issues): emitWarning: issue #<N> has open sub-issues — skipping close pipeline. Close sub-issues first., write askipped_open_sub_issuesoutcome entry viabin/issue-close-write-outcome.js, and skip the pipeline for this N. - All-N outcome entries (#695): after the pipeline completes or is skipped, ensure EVERY enumerated N has an outcome entry — including subsumed siblings that never ran a pipeline. Write missing entries with the appropriate skip state before the End report.
- Early-return outcome entries (#827): at any early-return path —
meta_pending_subsearly return, or a terminal-phase early return when triage reports the issue is already in its terminal state — write an outcome entry for that N before returning (states:skipped_meta_pending_subs,already_closed,skipped_open_sub_issues, as fits the branch).
What ships with it
6 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 e6a1382a8810
- 7d ago Changed 7fde4295234a
- 11d ago Changed 3aab86092ce6
- 17d ago Changed 80ab48e53624
- 21d ago Changed · -1 tokens per session 0fa0c22928d4
- 1mo ago Changed 6a4d70c659ac
- 1mo ago First seen · 101 lines · 74 tokens per session scan A 0c3ee487f6d3
issue-close-finalize is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 2,910 once invoked, about $0.0003 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…