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-startnpx skills add apokamo/kaji --skill issue-startgit 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-start)<a href="https://agentmods.dev/skills/apokamo/kaji/issue-start"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/issue-start.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.00037 | $0.01817 |
| Opus 5 | $0.00018 | $0.00908 |
| Sonnet 5 | $0.00007 | $0.00363 |
| Haiku 4.5 | $0.00004 | $0.00182 |
Grade A, and why
issue-start 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Start
イシュー対応を開始するためのworktreeをセットアップし、Issue本文にメタ情報を追記します。
いつ使うか
| タイミング | このスキルを使用 |
|---|---|
| コード/ドキュメント変更を伴うイシュー着手 | ✅ 必須 |
| 設計のみ（ファイル変更なし） | ⚠️ 任意 |
| 調査・リサーチのみ | ❌ 不要 |
重要: PRを作成する際やイシュー対応でコミットが必要な場合、git branch ではなくこのスキルを使用してください。
引数
$ARGUMENTS = <issue_id>
issue_id(必須): Issue番号 (例: 247 /local-pc1-3/gh:153)
第 2 引数は 廃止 されました（issue local-p1-17）。ブランチ prefix は
kaji issue context が返す branch_prefix（frontmatter branch_prefix →
type:* ラベル → chore fallback の優先順）から自動決定します。
命名規則
kaji issue context <issue_id> の出力（provider.resolve_issue_context() が正本）から
取得する branch_name / worktree_dir をそのまま使います。
- ブランチ名:
<branch_prefix>/<issue_id>(例:fix/247) - ディレクトリ:
<repo_root>/../kaji-<branch_prefix>-<issue_id>(例:../kaji-fix-247)
実行手順
Step 0: 引数の検査
$ARGUMENTS から issue_id を取得してください。第 2 引数（旧 prefix）が
渡された場合は ABORT verdict を出して停止し、廃止アナウンスをユーザに返してください
（label / frontmatter からの自動導出に一本化されているため）。
Step 1: context 正本の取得
system jq バイナリ依存を持ち込まないため、kaji issue context の -q (Python jq) を使う:
PREFIX=$(kaji issue context [issue_id] -q '.branch_prefix')
BRANCH=$(kaji issue context [issue_id] -q '.branch_name')
WT=$(kaji issue context [issue_id] -q '.worktree_dir')
worktree_dir は絶対パスで返ります。以降の手順では上記 3 変数を使います。
Step 2: ブランチとWorktreeの作成
メインリポジトリのルートから実行:
MAIN_REPO=$(git rev-parse --show-toplevel)
git worktree add -b "$BRANCH" "$WT" main
Step 2.5: venv シンボリックリンク作成
main プロジェクトの .venv へのシンボリックリンクを作成:
ln -s "$MAIN_REPO/.venv" "$WT/.venv"
これにより make check が即座に実行可能になります。
Step 2.6: provider overlay (.kaji/config.local.toml) シンボリックリンク作成
.kaji/config.local.toml は gitignored のため git worktree add では worktree に転写されない。
overlay 不在の worktree では kaji CLI が .kaji/config.toml の provider.type=github 既定値で動き、
local-* / gl:N 形式 ID が拒否される（codex 等が worktree 配下で kaji issue comment を
叩けず、レビュー判定の Issue 記録が欠落する原因）。
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 · 174 lines · 37 tokens per session scan A 43d695c6f74d
issue-start is a skill published in the GitHub repository apokamo/kaji (12 stars, last pushed 5d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,817 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.
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.
guardrails-ai-setup
Guardrails AI validation framework setup for LLM applications. Implement input/output validation, safety checks, and structured output enforcement.
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.