Borrowing it
Nothing to install: this file belongs to go-to-k/cdkd. 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/go-to-k/cdkd/main/.claude/skills/work-issues/SKILL.mdgit clone --depth 1 https://github.com/go-to-k/cdkdWrote 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/go-to-k/cdkd/work-issues)<a href="https://agentmods.dev/skills/go-to-k/cdkd/work-issues"><img src="https://agentmods.dev/badge/skills/go-to-k/cdkd/work-issues/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/go-to-k/cdkd/work-issues"><img src="https://agentmods.dev/badge/skills/go-to-k/cdkd/work-issues.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.00104 | $0.01763 |
| Opus 5.5 | $0.00042 | $0.00705 |
| Sonnet 5.5 | $0.00021 | $0.00353 |
| Haiku 4.5 | $0.00010 | $0.00176 |
Grade A, and why
work-issues 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 18d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Filed Issues
Drive as many OPEN issues as the run can carry to merged, released, installed fixes. The differentiator over "fix issue #N" is safe, collision-free PARALLELISM.
The golden rule: decide the set FIRST, claim it on the issues, THEN edit. The issue comment is the lock — it is what stops two agents fixing the same thing and colliding on the same file.
Launch mode: main checkout, or already inside a worktree
The flow creates one worktree per lane — right from the MAIN checkout, wrong
when the launch location is ALREADY a linked worktree (an Orca/ADE workspace, a
stray cd): git worktree add then NESTS one, and deleting the outer workspace
takes the inner directory and its uncommitted work with it.
The PARENT computes which case applies BEFORE stage 0: read
references/launch-mode.md and run the probe it holds (the ONLY copy).
- Before stage 0, because §2's collision scan consumes the answer: IN-PLACE its
relative
.claude/worktrees/<w>paths resolve to nothing and the scan reports an empty board, reading as "no competing agents". - In the PARENT, because stages 0–3 go to a read-only subagent whose return
payload carries no git state, so an answer computed there never reaches the
party running
git worktree add.
State all five printed values — MODE, which is MAIN-CHECKOUT or
IN-PLACE, plus LANE_TREE, MAIN_CHECKOUT, LAUNCH_BRANCH (the branch
§9 puts back; empty if launched detached) and ORIGIN (not go-to-k/cdkd
means a fork run) — in the opening report, written
after the probe and before any lane starts, and pass them into the triage
dispatch and every lane dispatch. That report is their only recorded copy.
IN-PLACE changes the collision scan's paths, the claim, the branch recipe,
the cleanup step, how main is reached, and where the retro branch is created;
references/launch-mode.md maps each consequence to the stage that fires it.
How this skill is packaged (read this before stage 0)
This file is a thin orchestrator; the procedure lives in per-stage files under
references/. Reading the stage file at stage entry is MANDATORY — the
summaries below are not executable on their own. A bare §N points into the
file that holds that section.
What ships with it
10 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.
- 18d ago Changed 5b8c27d4b83a
- 1mo ago Changed 3a5473b64d41
- 1mo ago Changed · +1 lines 1f440454c7f5
- 1mo ago Changed · -3 lines f18fbd743810
- 1mo ago Changed · -43 lines scan C → A 71655a8ec585
- 1mo ago Changed f23d04bfc167
- 1mo ago Changed · +3 lines ded933d1db59
- 1mo ago Changed · +1 tokens per session 7672a8913cf8
- 1mo ago Changed · +2 lines · -2 tokens per session 21378d71281a
- 1mo ago First seen · 159 lines · 105 tokens per session scan C c9b9f672565d
work-issues is a skill published in the GitHub repository go-to-k/cdkd (156 stars, last pushed today), licensed Apache-2.0. It adds 104 tokens to every session and 1,763 once invoked, about $0.0004 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
aws-cdk-mcp-server-mcp
AWS Cloud Development Kit (CDK) best practices, infrastructure as code patterns, and security compliance with CDK Nag.
next-task
End-to-end task pipeline. Discovers the next task, plans, implements, reviews with certainty-graded quality gates, then ships. Resumable via git state.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
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.