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 skills add theam/claude-dev-kit --skill issue-updategit clone --depth 1 https://github.com/theam/claude-dev-kitWrote 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/theam/claude-dev-kit/issue-update)<a href="https://agentmods.dev/skills/theam/claude-dev-kit/issue-update"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/issue-update/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/theam/claude-dev-kit/issue-update"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/issue-update.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.00068 | $0.01221 |
| Opus 5.5 | $0.00027 | $0.00488 |
| Sonnet 5.5 | $0.00014 | $0.00244 |
| Haiku 4.5 | $0.00007 | $0.00122 |
Grade A, and why
issue-update 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 25d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Update
Close the loop: after the code ships, the tracker must reflect it without anyone updating it by hand. This skill speaks to whichever tracker is configured in .claude/dev-kit.json (tracker.type).
Preconditions
.claude/dev-kit.jsonexists with atrackerblock (otherwise rundev-kit-setupfirst).- The adapter's backend is authenticated (MCP connector authorized, or
gh/azlogged in) — otherwise tell the user how to authenticate and stop. - A PR URL and a product-facing summary of the delivered work are available from the delivery flow.
1. Comment the delivery summary
Audience: product owners and other non-technical readers. The comment explains what was delivered and why, in user terms — no test counts, coverage percentages, lint, or tooling jargon. All technical evidence lives in the PR, which is linked.
Post a comment (via the adapter below) containing:
Pull request: <PR URL>
What was delivered:
- <the new behavior, described as a user would experience it — one bullet per acceptance criterion addressed>
Decisions taken:
- <each meaningful decision or interpretation made during implementation, in plain language, with the reason>
Out of scope / follow-ups:
- <anything deliberately left out or worth a future ticket, or "Nothing pending.">
Keep it factual and grounded in what was actually built — never a template filled with assumptions. If an acceptance criterion was NOT met, say so here plainly.
2. Ensure the item has a named owner
Every item carries a named owner: if it has no assignee, assign it to the current user. Agents act on a person's behalf — the item must always show whose behalf that is. (Skip only for trackers/flows where assignment is not applicable, and say so.)
3. Transition to review
Move the item to the team's review status. Never hardcode transition/state IDs — discover the available ones and pick the target named like "In Review" / "Code Review" / "Review"; if none matches, ask the user once and persist the choice under tracker.reviewState in .claude/dev-kit.json.
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.
- 25d ago Changed · +2 lines d6b06b8c5d1f
- 1mo ago First seen · 74 lines · 68 tokens per session scan A b56c73a4a2c4
issue-update is a skill published in the GitHub repository theam/claude-dev-kit (15 stars, last pushed 20d ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,221 once invoked, about $0.0003 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
triage-task
Reads a ticket from Jira or Azure DevOps and writes .workflow/ /triage.json. Use when asked what to work on, to pick up a ticket by key, or to understand its description, comments and blocking links.
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
outcome-roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
pm-planning
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.