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 shopwareLabs/ai-coding-tools --skill feature-branch-pr-writinggit clone --depth 1 https://github.com/shopwareLabs/ai-coding-toolsWrote 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/shopwarelabs/ai-coding-tools/feature-branch-pr-writing)<a href="https://agentmods.dev/skills/shopwarelabs/ai-coding-tools/feature-branch-pr-writing"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/feature-branch-pr-writing/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/shopwarelabs/ai-coding-tools/feature-branch-pr-writing"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/feature-branch-pr-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00152 | $0.02154 |
| Opus 5 | $0.00076 | $0.01077 |
| Sonnet 5 | $0.00030 | $0.00431 |
| Haiku 4.5 | $0.00015 | $0.00215 |
Grade A, and why
feature-branch-pr-writing 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 9d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature-Branch PR Description Drafting
Draft a PR title (conventional commit format) and description (narrative prose with topical subsections) for PRs targeting non-trunk feature branches. Analyzes the diff against the target branch, detects related PRs in the chain, and asks targeted questions for missing context.
Output scope: Presents formatted title + description text. Does not create or update PRs on GitHub. Does not write to any files.
Phase 1 — Assess Branch State
Determine what we're working with: branch, target, PR status, diff, and chain.
- Load
references/branch-and-pr-detection.mdand execute Steps 1-4. Route asfeature-branch-pr-writing. - Get the diff:
- If a PR exists: read its diff and changed files from GitHub (a GitHub MCP server, the
ghCLI, or the API — whatever the session has) - If no PR: run
git diff <target>...HEAD --statandgit log <target>..HEAD --oneline
- If a PR exists: read its diff and changed files from GitHub (a GitHub MCP server, the
- Chain detection: list PRs targeting the same feature branch (via the same GitHub access). Record titles, numbers, merge state, and any cross-references in bodies. Identify predecessor/successor relationships.
- Present a brief assessment to the user: branch name, target branch, PR status (exists / doesn't exist / has existing description), change magnitude (files touched, lines changed, areas affected), related PRs in the chain.
Phase 2 — Analyze Changes
Understand the full story of the branch relative to the target.
- Synthesize the full branch scope from the diff, commits, and file changes. Understand the totality: features, fixes, cleanups, refactors.
- Determine scope: map file paths to Shopware areas. This informs the conventional commit scope for the title.
| File path pattern | Scope |
|---|---|
src/Core/Checkout/Cart/ |
cart |
src/Core/Checkout/Order/ |
order |
src/Core/Checkout/Promotion/ |
promotion |
src/Core/Content/Product/ |
product |
src/Core/Content/Media/ |
media |
src/Core/Content/Category/ |
category |
src/Core/Content/Cms/ |
cms |
src/Core/Content/Mail/ |
mail |
src/Core/Framework/DataAbstractionLayer/ |
dal |
src/Core/Framework/App/ |
app-system |
src/Core/System/SystemConfig/ |
system-config |
src/Core/System/NumberRange/ |
number-range |
src/Storefront/ |
storefront |
src/Administration/ |
admin |
src/Elasticsearch/ |
elasticsearch |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 139 lines · 152 tokens per session scan A 6cbc5a61ddb8
feature-branch-pr-writing is a skill published in the GitHub repository shopwareLabs/ai-coding-tools (43 stars, last pushed yesterday), licensed MIT. It adds 152 tokens to every session and 2,154 once invoked, about $0.0008 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
release
This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and optionally publish to npm. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.
changelog
Ingest Claude Code changelog entries and integrate them into the current repo. Fetch (read-only display), diff (impact analysis, no edits), status (applied versions), and apply (full integrate pipeline, explicit user intent only). Use when: 'new cc version', 'what changed in claude code', 'apply changelog', a new CC…
apply
Apply a prior /repo-fleet-hygiene:audit action-plan JSON behind one fleet confirmation: default dry-run re-derives branch/worktree tips and prints the ordered batch; --apply mutates only after interactive confirmation or --yes. Owns batched merged-local-branch deletion with fail-closed OID refresh; cleans…
rename-references
Sweep stale references after renames, the syntactic forms token-only grep misses (slash-tokens, paths, chain prose, numbered table rows, frontmatter chains and globs). Use when: 'rename X to Y', 'I renamed X', 'audit rename', 'find stale refs', 'check for stragglers', 'after git mv', 'sweep references', 'rename impact…
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…