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/go-to-k/cdkd/create-prnpx skills add go-to-k/cdkd --skill create-prgit clone --depth 1 https://github.com/go-to-k/cdkdWrote 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/go-to-k/cdkd/create-pr)<a href="https://agentmods.dev/skills/go-to-k/cdkd/create-pr"><img src="https://agentmods.dev/badge/skills/go-to-k/cdkd/create-pr.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00031 | $0.00918 |
| Opus 5 | $0.00015 | $0.00459 |
| Sonnet 5 | $0.00006 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
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 5d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR
Run all quality checks and create a GitHub PR if everything passes.
Steps
-
Ensure on a feature branch with the right cwd:
git branch --show-current— check current branch- Multi-worktree pre-flight: if the current branch is
main(ormaster), also rungit worktree list --porcelainand check whether any other worktree is on a non-main branch. If yes, surface that explicitly:
The user almost certainly intended to rungit worktree list --porcelain | awk '/^worktree /{wt=$2} /^branch refs\/heads\//{b=substr($0,index($0,"refs/heads/")+11); if (b!="main" && b!="master") print wt " on branch " b}'/create-prfrom that worktree's path — every subsequentgit/gh pr viewcall defaults to cwd, so running from the parent worktree onmainproduces "no PR found for branch 'main'" even when a feature branch with commits is sitting in another worktree. Stop and ask the user whether to proceed in the listed worktree (offeringcd <path>as the next step) before falling through to "create a new branch". - If on
mainand no other worktrees have non-main branches, ask the user for a branch name and create it:git checkout -b <branch-name>. - Branch naming convention:
feat/,fix/,refactor/,docs/,chore/prefix. - Subsequent steps assume cwd is the worktree of the feature branch being PR'd. If the user defers the cd, abort instead of guessing.
-
Run
/verify-pr— typecheck, lint, build, tests, CI, docs consistency, leftover resources. If any check fails, stop and report. -
Ensure changes are committed and pushed:
git status— if uncommitted changes exist, ask the user whether to commit themgit push -u origin <branch>— ensure remote is up to date
-
Check if PR already exists for the current branch:
gh pr view --json number,url -q '.url' 2>/dev/null- If PR exists, report the URL and ask if the user wants to update it
-
Gather PR context:
git log main...HEAD --oneline— all commits in this branchgit diff main...HEAD --stat— changed files summary- Determine base branch (default:
main, overridable with--base)
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.
- 5d ago First seen · 70 lines · 31 tokens per session scan A 49ad00941b5a
create-pr is a skill published in the GitHub repository go-to-k/cdkd (132 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 918 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
aws-cdk-mcp-server-mcp
AWS Cloud Development Kit (CDK) best practices, infrastructure as code patterns, and security compliance with CDK Nag.
agent-squad-python
Use when building or modifying a Python app that uses the agent-squad Python package — async multi-agent orchestration for Python 3.11+: orchestrator, agents (BedrockLLMAgent, AnthropicAgent, OpenAIAgent, SupervisorAgent, GroundedAgent, ChainAgent, and more), classifier routing (Bedrock, Anthropic, OpenAI), storage…
agent-squad-typescript
Use when building or modifying a Node.js / TypeScript app that uses the agent-squad npm package — multi-agent orchestration: orchestrator, agents (all built-in types + GroundedAgent), classifier routing (Bedrock / Anthropic / OpenAI), storage (in-memory / DynamoDB / SQL), retrievers (Amazon KB / Dakera), and tools…
agent-squad-swift
Use when building or modifying a Swift app that uses the AgentSquad Swift framework — on-device multi-agent orchestration for iOS 16+ / macOS 14+: orchestrator, agents (Agent, GroundedAgent), classifier routing, LLM clients (OpenAI-compatible), tools (native + MCP), tool UIs/widgets, on-device storage, tracing, and…
nx-plugin-for-aws
Scaffold and build cloud-native applications on AWS using @aws/nx-plugin generators. Use when the user wants to create workspaces, generate projects, or scaffold infrastructure with the Nx Plugin for AWS.
aws-serverless-eda
AWS serverless and event-driven architecture expert based on Well-Architected Framework. Use when building serverless APIs, Lambda functions, REST APIs, microservices, or async workflows. Covers Lambda with TypeScript/Python, API Gateway (REST/HTTP), DynamoDB, Step Functions, EventBridge, SQS, SNS, and serverless…