Borrowing it
Nothing to install: this file belongs to cardstack/boxel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cardstack/boxel/main/.claude/skills/published-package-pr-title/SKILL.mdgit clone --depth 1 https://github.com/cardstack/boxelWrote 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/cardstack/boxel/published-package-pr-title)<a href="https://agentmods.dev/skills/cardstack/boxel/published-package-pr-title"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/published-package-pr-title/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/cardstack/boxel/published-package-pr-title"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/published-package-pr-title.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00104 | $0.01325 |
| Opus 5.5 | $0.00042 | $0.00530 |
| Sonnet 5.5 | $0.00021 | $0.00265 |
| Haiku 4.5 | $0.00010 | $0.00133 |
Grade A, and why
published-package-pr-title 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Published-Package PR Title
A conventional-commit prefix on a PR title is only meaningful for changes to a package this repo publishes to npm: packages/boxel-cli/**, packages/bxl/**, packages/glimmer-motion/**, packages/choreo/** and packages/choreo-player/**. There it's a binding contract that drives the version bump. Anywhere else it's noise — use a plain descriptive title.
The rule
- PR touches
packages/boxel-cli/,packages/bxl/,packages/glimmer-motion/,packages/choreo/orpackages/choreo-player/→ title MUST start with an allowed prefix followed by:(e.g.feat: add --watch flag to sync). - PR touches none of them → no prefix. Write a plain descriptive title (e.g.
Add evergreen-comments skill, notdocs: add evergreen-comments skill).
One title serves every published package. A PR touching several takes a single prefix, and each publish flow decides its bump from it independently.
glimmer-motion and @cardstack/choreo are a single flow: they release in lockstep at one shared version, because choreo peer-depends on the exact glimmer-motion version. One bump from the title applies to both, and a change that ships in either one publishes both.
Allowed prefixes and their bump level
The prefix determines the version bump applied post-merge:
| Prefix | Version bump |
|---|---|
any type with a ! (e.g. feat!:, fix!:, feat(cli)!:) or a BREAKING CHANGE: footer in the PR body |
major |
feat: |
minor |
fix:, perf:, refactor: |
patch |
chore:, docs:, test:, build:, ci:, style: |
none |
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 · 57 lines · 104 tokens per session scan A 9ba77d81ab7e
published-package-pr-title is a skill published in the GitHub repository cardstack/boxel (27 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 1,325 once invoked, about $0.0004 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-10-21.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.