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 dev-kit-setupgit 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/dev-kit-setup)<a href="https://agentmods.dev/skills/theam/claude-dev-kit/dev-kit-setup"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/dev-kit-setup/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/dev-kit-setup"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/dev-kit-setup.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.00081 | $0.02661 |
| Opus 5.5 | $0.00032 | $0.01064 |
| Sonnet 5.5 | $0.00016 | $0.00532 |
| Haiku 4.5 | $0.00008 | $0.00266 |
Grade A, and why
dev-kit-setup 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 24d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Kit Setup
Make the kit self-sufficient: detect the tracker, discover everything possible automatically, ask the user only for genuine choices, and persist the result so nobody on the team has to configure anything again.
When to run
.claude/dev-kit.jsondoes not exist (or lacks atrackerblock) and a kit skill (e.g.issue-fetch) needs it.- The user explicitly asks to set up or reconfigure the kit.
- A stored value turns out to be invalid (e.g. a field ID no longer exists) — re-discover just that value.
1. Determine the tracker
Pick tracker.type with the least friction:
- If the triggering reference makes it obvious, use it (
PROJ-1234/ENG-42→ Jira/Linear key style;#123→ GitHub/Azure). - Check which backends are actually available: is an Atlassian or Linear MCP authenticated? Is
ghlogged in for this repo? Is Azure DevOps configured? - If still ambiguous, ask the user once which tracker the team uses: Jira, Linear, GitHub Issues, or Azure DevOps.
Then run the matching discovery below. For any MCP/CLI that is not authenticated, offer to set it up for them (users are encouraged to just ask "connect my Jira" — do the work, don't only hand back a command):
- Claude Code: the tracker/design MCPs are plugin-declared (
atlassian,linear,figma) — authorize withclaude mcp login <server>(or tell them to run/mcpinside the session; the OAuth browser step is theirs to complete). - Codex: install the curated connector and have them sign in from the app —
codex plugin add atlassian-rovo@openai-curated(Jira/Confluence) ·linear@openai-curated·figma@openai-curated. - GitHub / Azure:
gh auth login/az login(no MCP).
Run the command for them when you can; the OAuth/browser sign-in is always the user's step. Then stop — never continue with invented values until the backend is actually reachable.
2. Discover per tracker
Jira
- Auth mode: default is the Atlassian MCP. If the Atlassian MCP is unavailable or blocked (not installed, not authorized, or disabled by an enterprise policy), set
authMode: "rest"and persist it — so the kit stops retrying the blocked MCP and uses REST from then on. In REST mode the kit calls the Jira REST API with credentials from the environment:JIRA_EMAIL+JIRA_API_TOKEN(Cloud, Basic auth) orJIRA_PAT(Server/DC, Bearer), plusJIRA_BASE_URL. Tell the user to put the credentials in.envand add.envto.gitignore— they never go in.claude/dev-kit.json. - Site: list accessible sites via the Atlassian MCP — one → use it; several → ask which. (In
restmode, useJIRA_BASE_URL/ the site the user gives.) - Project key: derive from the triggering ticket prefix and verify it exists; otherwise list projects and ask.
- Custom fields (auto-detect, no questions): resolve field IDs by matching names case-insensitively — Acceptance Criteria ("Acceptance Criteria"/"AC"), Sprint ("Sprint"), Story Points ("Story Points"/"Story point estimate"). If a name matches nothing, inspect a recent issue's custom fields; if still ambiguous, ask once showing the candidates. (In
restmode, resolve field IDs viaGET <base>/rest/api/3/field.)
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.
- 24d ago Changed · +2 lines 034a9a35572e
- 1mo ago First seen · 145 lines · 81 tokens per session scan A 8b49fd078467
dev-kit-setup is a skill published in the GitHub repository theam/claude-dev-kit (15 stars, last pushed 20d ago), licensed Apache-2.0. It adds 81 tokens to every session and 2,661 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.