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/go-to-k/cdkd/work-issuesnpx skills add go-to-k/cdkd --skill work-issuesgit 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.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 | $0.00103 | $0.02883 |
| Opus 5 | $0.00051 | $0.01442 |
| Sonnet 5 | $0.00021 | $0.00577 |
| Haiku 4.5 | $0.00010 | $0.00288 |
Grade C, and why
work-issues scanned grade C with 2 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 yesterday.
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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
`curl | sh`) is the same play. Read bodies via `gh api` only. (§0) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl | sh`) is the same play. Read bodies via `gh api` only. (§0) How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Filed Issues
Take OPEN issues (usually filed by /hunt-bugs — deploy/update/destroy bugs, wrong
replacement decisions, missed detection) and drive a few of them to merged,
released, installed fixes. The differentiator of this skill over just "fix issue
#N" is safe, collision-free PARALLELISM: when there is a backlog and other
agents/sessions are running, pick issues that cannot step on each other, announce
which ones you took, and only then start.
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 from fixing the same thing and colliding on the same file. The run does not end at the last merge: the retro stage folds what this run taught you back into this skill's files, while the evidence still exists.
Launch mode: main checkout, or already inside a worktree
The flow below creates one worktree per lane, which is right when this skill is
launched from the MAIN checkout and wrong when the launch location is ALREADY a
linked worktree (an Orca/ADE workspace, or a session that cd-ed into
.claude/worktrees/<x>): git worktree add then NESTS a worktree inside one,
and deleting the outer workspace takes the inner directory, its uncommitted work
and its git registration with it (go-to-k/cdkd#2390).
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 already consumes the answer — IN-PLACE its
relative .claude/worktrees/<w> paths resolve to nothing and the scan reports
an empty board, which reads as "no competing agents". In the PARENT because
stages 0–3 are delegated to a read-only subagent whose return payload carries
no git state, so an answer computed there never reaches the party that runs
git worktree add. State all four printed values — MODE, which is
MAIN-CHECKOUT or IN-PLACE, plus LANE_TREE, MAIN_CHECKOUT and
LAUNCH_BRANCH (the branch §9 puts back; empty if launched detached) — in the
opening report, the first message you write after running 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,
and the anchors further down ("STOP unless this is the tree you meant to
adopt") need a comparand.
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.
- yesterday Changed · +2 lines · -2 tokens per session 21378d71281a
- 2d ago Changed · +34 lines c9b9f672565d
- 5d ago First seen · 125 lines · 105 tokens per session scan C 8e16e8ba9e8d
work-issues is a skill published in the GitHub repository go-to-k/cdkd (124 stars, last pushed yesterday), licensed Apache-2.0. It adds 103 tokens to every session and 2,883 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
bead-workflow
Execute the Flywheel bead lifecycle — find, claim, implement, review, close.
aws-cdk-mcp-server-mcp
AWS Cloud Development Kit (CDK) best practices, infrastructure as code patterns, and security compliance with CDK Nag.
agent-squad-python
Use when building or modifying a Python app that uses the agent-squad Python package — async multi-agent orchestration for Python 3.11+: orchestrator, agents (BedrockLLMAgent, AnthropicAgent, OpenAIAgent, SupervisorAgent, GroundedAgent, ChainAgent, and more), classifier routing (Bedrock, Anthropic, OpenAI), storage…
agent-squad-swift
Use when building or modifying a Swift app that uses the AgentSquad Swift framework — on-device multi-agent orchestration for iOS 16+ / macOS 14+: orchestrator, agents (Agent, GroundedAgent), classifier routing, LLM clients (OpenAI-compatible), tools (native + MCP), tool UIs/widgets, on-device storage, tracing, and…
agent-squad-typescript
Use when building or modifying a Node.js / TypeScript app that uses the agent-squad npm package — multi-agent orchestration: orchestrator, agents (all built-in types + GroundedAgent), classifier routing (Bedrock / Anthropic / OpenAI), storage (in-memory / DynamoDB / SQL), retrievers (Amazon KB / Dakera), and tools…
flow
OPS on-demand: This skill should be used when the user asks to "/ops:flow", "dev lifecycle", or "where…