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/apokamo/kaji/issue-closenpx skills add apokamo/kaji --skill issue-closegit clone --depth 1 https://github.com/apokamo/kajiWrote 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/apokamo/kaji/issue-close)<a href="https://agentmods.dev/skills/apokamo/kaji/issue-close"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/issue-close.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.1 | $0.00032 | $0.06696 |
| Opus 5 | $0.00016 | $0.03348 |
| Sonnet 5 | $0.00006 | $0.01339 |
| Haiku 4.5 | $0.00003 | $0.00670 |
Grade A, and why
issue-close 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 6d 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 — 554 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Close
イシュー対応完了後のクリーンアップを実行します。 PR マージ、worktree 削除、ブランチ削除、Issue クローズを一括実行します。
いつ使うか
| タイミング | このスキルを使用 |
|---|---|
| PRがApproveされマージ可能 | ✅ 使用 |
| PRレビュー待ち | ❌ 待機 |
| 作業途中 | ❌ 不要 |
ワークフロー内の位置: implement → review-code → i-dev-final-check → i-pr → close
入力
ハーネス経由（コンテキスト変数）
常に注入される変数:
| 変数 | 型 | 説明 |
|---|---|---|
issue_id |
str | 正規化済み Issue ID（GitHub 数値または local ID） |
issue_ref |
str | 人間可読の Issue 参照（GitHub では #<issue_id>、local では bare ID） |
step_id |
str | 現在のステップ ID |
provider 解決時に追加で注入される変数:
| 変数 | 型 | 説明 |
|---|---|---|
provider_type |
str | github / local のいずれか。本 Skill の経路分岐に使用 |
default_branch |
str | ベースブランチ名（main 等）。local 経路で merge / push の引数に使用 |
branch_name |
str | フィーチャーブランチ名（feat/<id> 等） |
worktree_dir |
str | worktree 絶対パス |
手動実行（スラッシュコマンド）
$ARGUMENTS = <issue_id>
解決ルール
コンテキスト変数 issue_id が存在すればそちらを使用。
なければ $ARGUMENTS の第1引数を issue_id として使用。
issue_ref はハーネス経由ではプロンプトに自動注入される（prompt.py 側で provider 別に整形）。手動実行時は issue_id から導出する: GitHub 数値 ID なら #<issue_id>、local-* 形式なら bare ID（# を付けない）。
前提条件
/i-prでPRが作成済みであること- Merge commit方式を使用（ブランチ履歴を保持）
実行手順
[provider_type] に応じて手順が分岐する。
[provider_type]がgithub（または未注入の legacy 環境）→ 既存の Step 1〜6 を順に実行する（kaji pr merge/ worktree 削除 / branch 削除 /git pull/kaji issue close/ 報告）。[provider_type]がlocal→ 後述の provider=local の場合 セクションへ ジャンプし、design.md § local mode における /issue-close の手順 (6 step) を 実行する。github 用の Step 1〜6 は実行しない（PR 概念が無いため）。
共通: ワークフロー完了後の確認項目の移管
親 Issue を close する直前に、provider に関係なく本手順を実行する。
正本は
docs/dev/workflow_completion_criteria.md
§ follow-up Issue への移管、本文 template は
templates/follow-up-issue.md とする。
1. 未完了項目の抽出
親本文の ## 完了条件 内にある末尾サブセクション
### ワークフロー完了後の確認項目 だけを対象にし、次の ## 見出しまたは本文末尾までから
- [ ] の項目を抽出する。
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.
- 6d ago First seen · 554 lines · 32 tokens per session scan A 70ab9bc68596
issue-close is a skill published in the GitHub repository apokamo/kaji (12 stars, last pushed 5d ago), licensed Apache-2.0. It adds 32 tokens to every session and 6,696 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-30.
Other skills, from other repositories
assimilate-popular-workflows
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable…
mcp-app-verification
Comprehensive verification checklists for MCP Apps. Tests with basic-host reference, validates handler-before-connect, text fallback, resource URI linking, single-file bundling, host styling, CSP, and legacy pattern detection.
guardrails-ai-setup
Guardrails AI validation framework setup for LLM applications. Implement input/output validation, safety checks, and structured output enforcement.
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
cog-braindump-capture
Capture raw thoughts with automatic domain classification and vault routing.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.