Borrowing it
Nothing to install: this file belongs to AlexisBalayre/claude-code-power-config. 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/AlexisBalayre/claude-code-power-config/main/.claude/skills/pr-description/SKILL.mdgit clone --depth 1 https://github.com/AlexisBalayre/claude-code-power-configWrote 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/alexisbalayre/claude-code-power-config/pr-description)<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/pr-description"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/pr-description/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/alexisbalayre/claude-code-power-config/pr-description"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/pr-description.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.00059 | $0.01707 |
| Opus 5 | $0.00030 | $0.00853 |
| Sonnet 5 | $0.00012 | $0.00341 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
pr-description 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write a PR title and description
Setup: the tracker steps use an issue-tracker MCP server (the examples use a Linear-style API;
mcp__linear-server__*tool names are placeholders — swap them for your tracker's tools). The ticket prefix (PROJ) comes fromTRACKER_ISSUE_PREFIXin.env. No tracker? Skip step 2 and drop the ticket id everywhere.
Workflow
-
Gather context (run together):
git branch --show-current # MUST NOT be "main"; abort if it is git log main..HEAD --pretty=format:'%h %s%n%b' # commits on this branch git diff main...HEAD --stat # changed files + churn gh pr view --json number,url,state,title,body 2>/dev/null # non-zero exit = no PR yetRead the diff for the key files (
git diff main...HEAD -- <path>); on large diffs lean on--statplus the important files. -
Ground in the tracker (read-only). Grep branch + commit subjects for
PROJ-\d+. If found, fetch issue + parent epic withmcp__linear-server__get_issuefor What/Why and the canonical link. NEVER call anysave_*tool. No id: derive from diff + commits. -
Select sections from the diff (table below). Only include sections that apply.
-
Draft title + body together. Title per Title format; body to a temp file (
mktemp) per TEMPLATE.md. For an existing PR, treat the current title as a draft, not a constraint. -
Create or update the PR. Show the drafted title and body + the exact
ghcommand; quick confirm before running (notifies reviewers + CODEOWNERS) unless told to just do it.git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null || git push -u origin "$(git branch --show-current)" # update existing; pass --title only if it changes: gh pr edit <number> --body-file <tmp> [--title "<drafted title>"] # or create new: gh pr create --base main --title "<drafted title>" --body-file <tmp>
What ships with it
1 file 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 · 106 lines · 59 tokens per session scan A 4f7744137a25
pr-description is a skill published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 29d ago), licensed MIT. It adds 59 tokens to every session and 1,707 once invoked, about $0.0003 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-31.
Other skills, from other repositories
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
create-pr
Create evidence-backed pull requests to the GitHub main branch with strict preflight, quality, and security gates. Use when users ask to create/submit/open/update a PR to main (including private repos), decide draft vs ready state, and provide reviewer-ready context for team review.
git-commit
Safely create a git commit by validating repository state, staging intended changes, scanning for secrets/conflicts, generating a Conventional Commits message (repository convention first, else an English Angular default) from the staged diff, and committing without amend.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.