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.
curl -O https://raw.githubusercontent.com/apokamo/kaji/main/.claude/skills/series-create/SKILL.mdgit 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/series-create)<a href="https://agentmods.dev/skills/apokamo/kaji/series-create"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/series-create/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/apokamo/kaji/series-create"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/series-create.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00061 | $0.00759 |
| Opus 5.5 | $0.00024 | $0.00304 |
| Sonnet 5.5 | $0.00012 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
series-create 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 1mo 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Series Create
Generate a deterministic series YAML, validate it, show its dry-run plan, and stop before execution.
Input
Accept this manual form:
/series-create <issue>... --id <series-id> [--parent <issue>]
[--workflow <issue>=<repo-relative-path>]... [--update]
Preserve Issue order exactly. Treat --workflow as a member-specific override. Require --id and at
least one positive integer Issue number.
Workflow
-
Confirm
kaji config provider-typereturnsgithub; otherwise stop. -
Read each Issue without mutation:
kaji issue view <issue> --json labels,title,state -
Read every
.kaji/wf/official/**/*.yamland.kaji/wf/custom/**/*.yamldescriptionandrequires_providervalue. For each member without an override, select candidates whose description says they are the standard series auto-selection target for the Issue's singletype:label and whose provider isgithuborany. -
Auto-select only when exactly one candidate remains. Display the Issue type and matching description sentence as the reason. If the Issue has zero or multiple
type:labels, or the candidate count is not one, stop and request--workflow <issue>=<path>for that member. -
Invoke the deterministic generator. Do not write YAML manually:
python -m kaji_harness.scripts.series_generate \ --id <series-id> [--parent <parent>] \ --member <issue>=<workflow>... \ --output .kaji/series/<series-id>.yaml [--update] -
If the target exists without
--update, stop. Never retry with--updateimplicitly. -
Run both checks and stop if either fails:
kaji validate-series .kaji/series/<series-id>.yaml kaji run-series .kaji/series/<series-id>.yaml --dry-run -
Report the generated path, ordered members, workflow selection reasons, validation result, and dry-run plan. Do not start
kaji run-serieswithout--dry-run.
Output
- One
.kaji/series/<id>.yamlcontaining onlyid, optionalparent_issue,strategy, orderedmemberswith resolved workflow paths, andon_failure. - A console summary of selection reasons and the validated dry-run plan.
- No Issue, PR, label, sub-issue, state, lock, or member-run mutation.
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.
- 1mo ago First seen · 80 lines · 61 tokens per session scan A a0680f06a3d8
series-create is a skill published in the GitHub repository apokamo/kaji (15 stars, last pushed 5d ago), licensed Apache-2.0. It adds 61 tokens to every session and 759 once invoked, about $0.0002 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-30.
Other skills, from other repositories
software-design-lifecycle-delivery
Use when an architect must decide which architecture lifecycle stage to enter next, route to the correct stage methodology skill, and apply the merged lifecycle backbone as one coherent delivery chain rather than as separate old and new skill systems.
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip-board
Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.
first-task
Guide the user's first Paperclip task when its description invokes /first-task. Interpret the opening answer, clarify their goal, propose a plan or a single task, and wait for approval before hiring agents or executing approved work.
summarize-status
Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.