kaji: Skill for Claude Code

.claude/skills/herdr-kaji-launch/SKILL.md

herdr-kaji-launch is a skill for Claude Code, Codex from apokamo/kaji. It costs 64 tokens per session (636 once invoked), scanned A, original, Apache-2.0.

A procedure for opening a related Herdr terminal pane and starting the kaji workflow there. Herdr is a terminal environment with multiple panes, and kaji is the requested interactive command.

In plain words
What is it for?
Use it when an agent running inside Herdr must start, display, or hand off a kaji workflow in a sibling pane.
Why use it?
It provides a defined handoff location while preserving the current working folder and terminal focus.

Skill for Claude CodeCodex

Written for Claude Code and Codex: installed under .claude/, but also agents/openai.yaml present. Also seen: mentions Claude Code; mentions Codex.

This is apokamo/kaji's own configuration. It tells Claude Code and Codex how to work on kaji itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kaji configures →

Reuse

Borrowing it

Nothing to install: this file belongs to apokamo/kaji. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/apokamo/kaji/main/.claude/skills/herdr-kaji-launch/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/apokamo/kaji

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for herdr-kaji-launch

README.md
[![agentmods](https://agentmods.dev/badge/skills/apokamo/kaji/herdr-kaji-launch/github.svg)](https://agentmods.dev/skills/apokamo/kaji/herdr-kaji-launch)
Your own site
<a href="https://agentmods.dev/skills/apokamo/kaji/herdr-kaji-launch"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/herdr-kaji-launch/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.

agentmods 80×15 button for herdr-kaji-launch

Your own site · 80×15
<a href="https://agentmods.dev/skills/apokamo/kaji/herdr-kaji-launch"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/herdr-kaji-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 636 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.00636
Opus 5 $0.00032 $0.00318
Sonnet 5 $0.00013 $0.00127
Haiku 4.5 $0.00006 $0.00064

Measured 12d ago against content hash 7685026fa96e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

herdr-kaji-launch 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 12d 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.

.claude/skills/herdr-kaji-launch/SKILL.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Herdr Kaji Launch

Launch kaji in a response-identified sibling pane while preserving the caller's cwd and focus.

Input

Use the kaji command requested by the user. For kaji run, require a workflow path and Issue ID. Unless the user explicitly supplied equivalent options, add:

--agent-runner interactive-terminal --interactive-terminal-backend herdr

Procedure

  1. Check HERDR_ENV=1 and a non-empty HERDR_PANE_ID. If either check fails, stop and tell the user to start this agent inside Herdr. Do not inspect or control the UI-focused session from outside Herdr.

  2. If the release-matched Herdr skill is not already in context, run herdr --skill and read its complete output before any pane operation. Follow its guardrails if they are stricter than this skill.

  3. Resolve the intended cwd. Default to the caller's current working directory; use a different cwd only when the user supplied it or the target worktree was resolved explicitly.

  4. Split from the explicit caller pane with --no-focus and parse the new pane ID from the JSON response. Never predict an ID and never omit the target.

    herdr pane split "$HERDR_PANE_ID" \
      --direction right \
      --ratio 0.5 \
      --cwd "$PWD" \
      --no-focus
    
  5. Build one shell-quoted interactive kaji command from the user's arguments and run it in the response-derived pane ID.

    herdr pane run "<response-pane-id>" \
      "kaji run <workflow> <issue> --agent-runner interactive-terminal --interactive-terminal-backend herdr"
    
  6. Report the pane ID, cwd, and exact kaji argv to the user. Leave the pane open for interaction. Close it only if the user asks, and only after re-reading that exact pane ID.

Invariants

  • Launch kaji as a real interactive command. Do not invoke claude -p, Claude Code print mode, or any headless substitute for this path.
  • Do not use agent start for kaji; kaji is the command running in the pane, not the Herdr-recognized coding-agent occupant.
  • Do not use terminal output matching as workflow completion authority. The nested interactive runner advances on its own verdict.yaml artifacts.
  • Do not install Herdr integrations or plugins as part of launching kaji.
  • Do not close, prune, or reuse any pane whose ID did not come from this split response.

Read the full file on GitHub · 61 lines

Files

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.

Changes

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.

  1. 12d ago First seen · 61 lines · 64 tokens per session scan A 7685026fa96e

Subscribe to this mod's changes

herdr-kaji-launch is a skill published in the GitHub repository apokamo/kaji (12 stars, last pushed 4d ago), licensed Apache-2.0. It adds 64 tokens to every session and 636 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

software-design-lifecycle-tech-detailed-methodology

Use when an architect must run the detailed-design portion of technical design, preserve the full lifecycle-stage doctrine for detailed design, and define the concrete runtime, project, flow, data, interface, non-functional, security, recovery, hardware, and implementation-plan surfaces needed for execution.

xiaohei-info/oh-my-multica · 65 tokens

software-design-lifecycle-solution-design-biz-arch-diagramming

A method for designing and reviewing a business-solution architecture: a middle-level view that connects confirmed business problems to a solution before technical implementation is designed.

xiaohei-info/oh-my-multica · 57 tokens

software-design-lifecycle-tech-overview-system-arch-diagramming

A guide for architects who draw or review system architecture diagrams during overview design. It explains subsystems, outside dependencies, communication links, and system boundaries without going into every technology detail.

xiaohei-info/oh-my-multica · 49 tokens

creative-claude-design

Design one-off HTML artifacts (landing, deck, prototype).

xiaohei-info/oh-my-multica · 18 tokens

diagram-drawio

Use when the user requests diagrams, flowcharts, architecture diagrams, ER diagrams, UML / sequence / class diagrams, network topology, ML/DL model figures (Transformer/CNN/LSTM), mind maps, or any visualization. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that…

xiaohei-info/oh-my-multica · 120 tokens

software-development-norms

Use when writing, reviewing, or refactoring code in any language to apply industrial-grade development norms abstracted from the Alibaba Java Development Handbook. Covers naming, type safety, exceptions, logging, concurrency, databases, project structure, testing, and security with language-agnostic principles and…

xiaohei-info/oh-my-multica · 66 tokens