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 surajssd/dotfiles --skill pr-descriptiongit clone --depth 1 https://github.com/surajssd/dotfilesWrote 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/surajssd/dotfiles/pr-description)<a href="https://agentmods.dev/skills/surajssd/dotfiles/pr-description"><img src="https://agentmods.dev/badge/skills/surajssd/dotfiles/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/surajssd/dotfiles/pr-description"><img src="https://agentmods.dev/badge/skills/surajssd/dotfiles/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.00053 | $0.01396 |
| Opus 5.5 | $0.00021 | $0.00558 |
| Sonnet 5.5 | $0.00011 | $0.00279 |
| Haiku 4.5 | $0.00005 | $0.00140 |
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 1mo 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate PR Description
Analyze the current branch's commits and diffs against the default branch, optionally use a PR template, and output a well-formatted PR description.
Step 1: Determine the default branch
Try to find the default branch name:
git rev-parse --verify main >/dev/null 2>&1
If main exists, set DEFAULT_BRANCH=main.
Otherwise, try master:
git rev-parse --verify master >/dev/null 2>&1
If master exists, set DEFAULT_BRANCH=master.
If neither exists, try to detect via the remote HEAD:
git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's|refs/remotes/origin/||'
If this returns a branch name, use that as DEFAULT_BRANCH.
If no default branch can be determined, report "❌ Could not determine the default branch (tried main, master, and origin HEAD)" and stop.
Step 2: Gather commits and diffs
Run the following commands to collect change information:
-
Full commit log with diffs (for deep analysis):
git log $DEFAULT_BRANCH..HEAD -p --reverse -
File change summary (for the overview):
git diff $DEFAULT_BRANCH..HEAD --stat -
One-line commit list (for reference):
git log $DEFAULT_BRANCH..HEAD --format="%h %s"
If no commits are found between $DEFAULT_BRANCH and HEAD (i.e., the output is empty), report "❌ No commits found between $DEFAULT_BRANCH and HEAD. Make sure you are on a feature branch with commits ahead of $DEFAULT_BRANCH." and stop.
Step 3: Search for a PR template
Check for a PR template in these locations, in priority order, using the Glob tool:
.github/PULL_REQUEST_TEMPLATE.md.github/pull_request_template.mdPULL_REQUEST_TEMPLATE.md(repo root)pull_request_template.md(repo root)docs/PULL_REQUEST_TEMPLATE.mddocs/pull_request_template.md.github/PULL_REQUEST_TEMPLATE/directory (if it exists, list all.mdfiles inside and use the first one)
Use glob patterns like **/{PULL_REQUEST_TEMPLATE,pull_request_template}.md to search efficiently.
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.
- 1mo ago First seen · 153 lines · 53 tokens per session scan A 63b36f66a83b
pr-description is a skill published in the GitHub repository surajssd/dotfiles (5 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,396 once invoked, about $0.0002 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-08-31.
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…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.