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/christopher-buss/bedrock/create-prnpx skills add christopher-buss/bedrock --skill create-prgit clone --depth 1 https://github.com/christopher-buss/bedrockWrote 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/christopher-buss/bedrock/create-pr)<a href="https://agentmods.dev/skills/christopher-buss/bedrock/create-pr"><img src="https://agentmods.dev/badge/skills/christopher-buss/bedrock/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.00040 | $0.00622 |
| Opus 5 | $0.00020 | $0.00311 |
| Sonnet 5 | $0.00008 | $0.00124 |
| Haiku 4.5 | $0.00004 | $0.00062 |
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open a pull request for the already-committed, already-pushed branch. This skill creates the PR only — it never commits, pushes, or renames a branch.
1. Read the diff
Resolve the base branch first: gh repo view --json defaultBranchRef. Then read the change against it:
git diff <base>...HEAD --name-status
git log <base>...HEAD --oneline
git diff <base>...HEAD
Capture every issue the commits reference (#NNN, closes #NNN, fixes #NNN).
Done when you can name the change type, the systems touched, and every referenced issue.
2. Guard preconditions
This skill opens the PR and nothing else.
- Uncommitted changes (
git status) or a branch with no remote → stop, surface it to the user, do not auto-fix.
Done when the tree is clean and the branch exists on the remote.
3. Title
type(scope): imperative description
Conventional commit, issue number appended when one is referenced. Derive it from the diff, not the branch name. Types: feat, fix, refactor, chore, docs, test, perf, ci.
4. Body
Prefer a project template if one exists — .github/PULL_REQUEST_TEMPLATE.md, .github/pull_request_template.md, or a file under .github/PULL_REQUEST_TEMPLATE/. Fill it from the diff. Otherwise build the body from these sections:
## Summary
[2–5 specific sentences: what changed and why.]
## References
Closes #NNN
Parent: #NNN
- Summary — concrete, not generic.
- Manual verification — add this section only for checks CI can't run. Omit it when there is nothing manual to report. Never restate automated test, coverage, or lint results — CI owns those.
- References —
Closes #NNNfor each issue the PR resolves. Link a parent PRD withParent: #NNN, orCloses #NNNwhen this is its final slice.
Done when every commit-referenced issue is accounted for in the body.
5. Create
gh pr create --title "<title>" --body "<body>" --base <base>
Base is the detected default branch. Open ready-for-review unless the changes are clearly WIP or the user asked for a draft, in which case add --draft. Honor any base or title the user supplied.
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 · 68 lines · 40 tokens per session scan A 168a61a93f2c
create-pr is a skill published in the GitHub repository christopher-buss/bedrock (14 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 622 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-09-01.
Other skills, from other repositories
pulumi-migrate-from-discovered-stack
Migrate a CloudFormation or ARM stack into a Pulumi stack, sourced from a stack that Pulumi Cloud's Discovery feature has already found and exposed via the discovered-stacks API. Load this skill when the user has a discovered stack in Pulumi Cloud and wants to bring its resources under Pulumi management. Do NOT load…
pulumi-component
Guide for authoring Pulumi ComponentResource classes. Use when creating reusable infrastructure components, designing component interfaces, setting up multi-language support, or distributing component packages.
pulumi-overview
Use this skill for any task that creates, modifies, inspects, or destroys cloud infrastructure or SaaS configuration, from one-off CLI operations to full multi-resource projects, across providers in the Pulumi ecosystem. A typical project spans many providers (AWS or Azure or GCP, Kubernetes, Cloudflare, Auth0…
provider-upgrade
Upgrade any Pulumi provider to a newer version and reconcile the resulting diff. Use when users want to upgrade or update a provider (including editing package.json, requirements.txt, pyproject.toml, go.mod, or Pulumi.yaml to bump a provider SDK), check for breaking changes before or during an upgrade, fix resources…
pulumi-best-practices
Load when the user is writing, reviewing, or debugging Pulumi TypeScript/Python programs; asks about Output or apply() usage; wants to create ComponentResource classes; needs to refactor resources without destroying them (aliases); is setting up secrets or config; or is configuring a pulumi preview/up CI workflow.…
pulumi-arm-to-pulumi
Convert or migrate Azure ARM (Azure Resource Manager) templates, Bicep templates, or code to Pulumi, including importing existing Azure resources. This skill MUST be loaded whenever a user requests migration, conversion, or import of ARM templates, Bicep templates, ARM code, Bicep code, or Azure resources to Pulumi.