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/create-prnpx skills add theam/claude-dev-kit --skill create-prgit 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.00048 | $0.01321 |
| Opus 5 | $0.00024 | $0.00660 |
| Sonnet 5 | $0.00010 | $0.00264 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade A, and why
create-pr 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 2d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR
Final step of the story workflow. Runs when the applicable gates pass (gates are adaptive to the project — see instructions/testing-standards.md).
Preconditions (verify, do not assume)
- Unit tests for touched files pass — when the project has a test framework.
coverage-checkpasses — when the project has coverage tooling (project's bar, default ≥ 95%, no regression).- Related e2e tests pass — when the project does e2e (
e2e-generateran for user-facing changes). - Lint passes for touched files — when the project lints.
- A
pr-review-style self-review found no unresolved blocking findings. - Security pass has no blocking findings (always applies).
A gate that does not apply (no test/e2e/lint setup) is not a blocker — but it must be called out in the PR "How it was verified" section as not applicable, recommend adding, never omitted. A gate that applies and fails stops the PR: report what's missing instead of opening it. (A gates policy in .claude/dev-kit.json can force required/off.)
Branch & commit
- Branch from the repo's default integration branch. Naming:
<type>/<TICKET-KEY>-<short-slug>(e.g.feat/PROJ-1234-payment-status-filter). Follow the repo's convention if one exists. - Stage only files related to the story. List anything intentionally left out.
- Commit message:
<type>: <TICKET-KEY> <imperative summary>plus a short body of key changes. Follow the repo's convention if one exists.
Pull request
Open the PR on the configured host (prHost in .claude/dev-kit.json; default github). Branch/commit/push are the same everywhere (plain git); only the "open the PR" call differs:
- github —
gh pr create(ghauthenticated). - bitbucket — push the branch, then create the PR via the REST API:
POST https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pullrequestswith{title, source:{branch:{name}}, destination:{branch:{name}}}, authenticated with a Bitbucket app password / access token from the environment (e.g.BITBUCKET_TOKEN). TheacliCLI works too if the team uses it. Derive{workspace}/{repo_slug}from theoriginremote. - gitlab —
glab mr create(glabauthenticated). - azure —
az repos pr create --source-branch <branch> --target-branch <base> --title <title> --description <body>(Azure CLI with theazure-devopsextension,az loginauthenticated; runaz extension add --name azure-devopsonce if missing). The org/project/repo come from theoriginremote oraz devops configure --defaults. - other/none — print the branch and the ready-to-paste PR title/body and let the user open it.
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.
- 2d ago First seen · 86 lines · 48 tokens per session scan A bc92ed991664
create-pr is a skill published in the GitHub repository theam/claude-dev-kit (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 48 tokens to every session and 1,321 once invoked, about $0.0002 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
meridian-etl
Debug and work with Meridian's ETL pipeline. Covers session boundary detection, cursor management, DB queries, and common failure modes.
meridian-mcp
Build, configure, and debug the Meridian MCP server. Exposes app session data to AI tools via the Model Context Protocol.
session-summary
You summarise ONE work-burst of a developer's coding-agent session. The goal is to capture what the developer actually worked on, and why it mattered, so that a PM, a teammate, or the developer themselves can immediately understand the purpose and the outcome at a glance — without reading the transcript.
pir-action-tracker
Parses Post-Incident Review (PIR) pages in a Confluence space, fetches live status from referenced Jira tickets, updates action item tables with current status and due dates, marks completed PIRs with a visual closure panel, and surfaces any overdue actions for follow-up. Designed for Customer Success, Support, and…
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-service-management
Complete ITSM/ITIL workflow support for JSM - service desks, requests, SLAs, customers, approvals, knowledge base. Use when managing service desk requests, tracking SLAs, or handling customer operations.