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 session-closegit 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/session-close)<a href="https://agentmods.dev/skills/nirecom/agents/session-close"><img src="https://agentmods.dev/badge/skills/nirecom/agents/session-close/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/session-close"><img src="https://agentmods.dev/badge/skills/nirecom/agents/session-close.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.00051 | $0.02531 |
| Opus 5.5 | $0.00020 | $0.01012 |
| Sonnet 5.5 | $0.00010 | $0.00506 |
| Haiku 4.5 | $0.00005 | $0.00253 |
Grade A, and why
session-close scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- `/issue-close-finalize` is invoked via the Skill tool only (never `bash`/`spawnSync`). How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session close orchestrator. Drives issue-close-finalize (when applicable),
collects the outcome JSON written by its ICF-K, and emits the Final Report by
substituting the skeleton from hooks/lib/final-report-schema.renderSkeleton.
Replaces the legacy "Step 7" emit inside /worktree-end so the Final Report
reflects every terminal action.
Pre-flight
AGENTS_MAIN_ROOTmust be set.- Caller context (pull_request path):
/worktree-endWE-1..WE-18a have already completed (PR merged, worktree removed;<CONTROL_DIR>/final-report-env.jsonexists). - Caller context (direct: merge_to_main is complete):
/merge-to-mainpushed to the default branch. No worktree-end ran; the env file does not yet exist.
SC-0 — Resolve PLANS_DIR and session id
Run bash "$AGENTS_MAIN_ROOT/bin/workflow-plans-dir" once as one bare command — never assigned to a variable and echoed back. Canonical: skills/_shared/resolve-plans-dir.md.
Substitute the absolute path it prints for <PLANS_DIR> in every subsequent step.
Resolve <session-id> from $CLAUDE_CODE_SESSION_ID with the fallback chain used by --from-session. If unresolvable, abort:
session id unresolved — cannot render Final Report. <CONTROL_DIR> is the stdout of node "$AGENTS_MAIN_ROOT/bin/workflow-control-dir" --session <session-id> --for-write (non-zero → abort).
<PLANS_DIR>, <CONTROL_DIR> and <session-id> are LLM-substituted literals — shell variables
do not persist between Bash tool calls.
SC-1 — Detect the route
Run: node "$AGENTS_MAIN_ROOT"/bin/session-close-detect-route.js --session ""
ROUTE=wf-meta→ WF-META session. RecordIS_WF_META=yesas an LLM-tracked state literal (not a shell variable — every Bash call is self-contained). Proceed to SC-2C.ROUTE=pull_request→ worktree path (SC-2A).ROUTE=direct→ direct delivery path (SC-2B).
SC-2A — Worktree path: reuse existing env JSON
test -f "<CONTROL_DIR>/final-report-env.json" \
|| { echo "ERROR: env JSON missing — /worktree-end must run first" >&2; exit 1; }
What ships with it
2 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 d7577ab27341
- 7d ago Changed · -9 lines · +1 tokens per session 8b5c92bbcbfc
- 9d ago Changed b05f6b7490e7
- 11d ago Changed 67dc7eaff79c
- 14d ago Changed · +4 lines 028ca8f8d4f9
- 17d ago Changed · -1 lines 5270c508d57d
- 21d ago Changed 7321fc3cb86a
- 1mo ago Changed · -5 lines 93937ecf6b2b
- 1mo ago Changed · -4 lines c9c3c18f4dd0
- 1mo ago First seen · 199 lines · 50 tokens per session scan A e5e76205660a
session-close is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 2,531 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). 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…