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/tomzx/agents/create-pr-descriptionnpx skills add tomzx/agents --skill create-pr-descriptiongit clone --depth 1 https://github.com/tomzx/agentsWhat 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.00028 | $0.00920 |
| Opus 5 | $0.00014 | $0.00460 |
| Sonnet 5 | $0.00006 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
create-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 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate PR Description
Generates a structured PR description from the current branch's diff against its Graphite parent, optionally cross-referencing a GitHub issue to assess acceptance criteria coverage.
Prerequisites
gt(Graphite CLI) installed and authenticated in a git repositoryghCLI authenticated (required only when$1and$2are provided)- Current branch must have commits relative to its parent
Note: This skill uses the Graphite CLI (
gt) and diffs against the Graphite parent branch. For agh-based workflow that diffs against the git merge base and creates the PR directly, use/create-prinstead.
Skill attribution (GitHub)
Before returning the PR description, read github-post-attribution/SKILL.md and append the Generated with footer for SKILL_DIR = create-pr-description to the end of the description body. This footer travels with the description when the user posts it to GitHub via gh pr create or gh pr edit.
Workflow
Compute diff (gt parent -> HEAD)
|
v
Issue provided? ($1 $2)
/ \
Yes No
| |
v v
Fetch issue Skip issue
details lookup
| |
v |
Assess |
acceptance |
criteria |
| |
+------+------+
|
v
Generate PR description markdown
Steps
- Compute the diff:
git diff $(gt parent)..HEAD - If
$1(repository) and$2(issue number) are provided, fetch the issue:gt issue view $2 --repo $1 - Resolve agents attribution per
github-post-attribution/SKILL.md: computeSKILL_COMMIT,SKILL_SHORT_SHA,SKILL_FILE_URL, and{BASE}forSKILL_DIR=create-pr-description. - Generate the PR description following the output format below, substituting the resolved
SKILL_FILE_URLandSKILL_SHORT_SHAinto the footer. - Return the result inside a markdown code block with each sentence on its own line. Do not line wrap the description; each paragraph/bullet should be a single long line.
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 · 118 lines · 28 tokens per session scan A dbe06fdd6db3
create-pr-description is a skill published in the GitHub repository tomzx/agents (5 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 920 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…