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 create-prgit 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/create-pr)<a href="https://agentmods.dev/skills/theam/claude-dev-kit/create-pr"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/create-pr/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/create-pr"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/create-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 32 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 32 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00048 | $0.01469 |
| Opus 5.5 | $0.00019 | $0.00588 |
| Sonnet 5.5 | $0.00010 | $0.00294 |
| Haiku 4.5 | $0.00005 | $0.00147 |
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 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 — 88 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
Before creating, check the branch doesn't already have an open PR (gh pr view <branch> --json number,state,url, or gh pr list --head <branch> --state open). If one is open, update it instead of opening a duplicate. If the only PR for the branch is closed/merged, do not reuse its number — push to a fresh branch and open a new PR. Never assume a PR number from earlier in the session.
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:
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 818f1ee9a7e1
- 1mo 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 (15 stars, last pushed 20d ago), licensed Apache-2.0. It adds 48 tokens to every session and 1,469 once invoked, about $0.0002 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
draft-pr
Writes a PR title and description to .workflow/ /pr.md from the branch's commits, the plan and the recorded verification. Use when opening a PR or asked for a PR description.
address-review
Turns PR review comments into a triaged change list, applies the accepted ones, and drafts replies to .workflow/ /review-response.md. Use when a PR has feedback to work through.
write-commit
Writes a commit message in the repo's own convention, validated and saved to .workflow/ /commit.txt. Use when asked to commit, or to write or fix a commit message.
run
The single lifecycle entry point — take one or more tickets and drive each through its whole lifecycle (investigate, red tests, implement, gates, review, PR, merge, archive), interleaving them. Lean by default — one worker per ticket runs red tests, implementation and the gate scripts in one worktree, then…
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.