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/theam/claude-dev-kit/dev-kit-setupnpx skills add theam/claude-dev-kit --skill dev-kit-setupgit clone --depth 1 https://github.com/theam/claude-dev-kitWhat 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.00081 | $0.02418 |
| Opus 5 | $0.00041 | $0.01209 |
| Sonnet 5 | $0.00016 | $0.00484 |
| Haiku 4.5 | $0.00008 | $0.00242 |
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 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.
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 — 145 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
- Site: list accessible sites via the Atlassian MCP — one → use it; several → ask which.
- 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.
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 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 (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 81 tokens to every session and 2,418 once invoked, about $0.0004 per session on Opus 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
jira-administration
Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.
jira-custom-fields
Custom field discovery and configuration. TRIGGERS: 'field ID for', 'what's the field ID', 'what is the field ID', 'list custom fields', 'what fields are available', 'what custom fields', 'show custom fields', 'customfield', 'find field', 'agile fields', 'configure agile fields', 'story points field'. Use for JIRA…
jira-agile-management
Epic creation and sprint management - create epics, manage sprints, view backlog, estimate with story points. TRIGGERS: 'create an epic', 'create epic', 'new epic', 'show the backlog', 'view backlog', 'add to sprint', 'move to sprint', 'set story points', 'sprint planning', 'epic for', 'link to epic', 'sprint list'…
jira-assistant
JIRA automation hub routing to 13 specialized skills for any JIRA task: issues, workflows, agile, search, time tracking, service management, and more.
stale-ticket-triage
Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.
development
AllBeads development process. Use when planning features, creating documentation, tracking work with beads, or understanding the documentation system.