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/eveld/claude/write-pr-descriptionnpx skills add eveld/claude --skill write-pr-descriptiongit clone --depth 1 https://github.com/eveld/claudeWrote 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/eveld/claude/write-pr-description)<a href="https://agentmods.dev/skills/eveld/claude/write-pr-description"><img src="https://agentmods.dev/badge/skills/eveld/claude/write-pr-description.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00476 |
| Opus 5 | $0.00011 | $0.00238 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
write-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 3d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write PR Description
Create structured pull request descriptions that provide context for reviewers.
Template
See templates/pr-description.md for the full template structure.
Sections
Summary
- 1-2 sentences explaining the PR at a high level
- What is being added/fixed/changed
- Why it matters
What Changed
- Bullet list of specific changes
- Focus on "what" not "how"
- Group related changes together
Why
- Business context or technical motivation
- Problem being solved
- Why this approach was chosen
Screenshots (if applicable)
- Before/after comparisons for UI changes
- Error states
- Different screen sizes/browsers
Related Issues
- Link to tickets:
Closes #123 - Link to related PRs:
Refs #456 - Link to documentation
Example
## Summary
Adds JWT token refresh mechanism to prevent unexpected session expiration. Tokens are automatically refreshed 5 minutes before expiry.
## What Changed
- Added token refresh endpoint `/api/auth/refresh`
- Implemented automatic refresh timer in auth middleware
- Added token expiry checking logic
- Updated auth context to handle refresh flow
- Added tests for refresh scenarios
## Why
Users were experiencing unexpected logouts when their sessions expired during active use. This caused data loss and poor UX. Automatic token refresh keeps sessions alive as long as users are active.
## Related Issues
Closes #123
Integration with Git Workflow
When user asks to create PR or you're following git workflow:
- Review all commits in the branch
- Read git diff to understand full scope of changes
- Draft PR description following structure
- Use
gh pr createwith body in heredoc:
gh pr create --title "feat(auth): add JWT token refresh" --body "$(cat <<'EOF'
## Summary
...
## What Changed
...
EOF
)"
Benefits
- Reviewers understand context quickly
- Clear explanation of what and why
- Focused on changes and motivation
- No duplicate test/verification information
- Easy to reference later
- Better PR discussions
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.
- 3d ago First seen · 89 lines · 22 tokens per session scan A cc046fbec2aa
write-pr-description is a skill published in the GitHub repository eveld/claude (10 stars, last pushed 7mo ago), licensed MIT. It adds 22 tokens to every session and 476 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
code-indexing-pipeline
How Infigraph turns source into a graph — adding a language (tree-sitter vs ANTLR grammar-plugin), cross-file call resolution, SCIP compiler-grade enrichment, and file-watch/reindex triage. Use when adding language support, debugging unresolved calls or SCIP import, or triaging stale index/watcher issues.
analysis-subsystems
How Infigraph's multi-repo/group mode and taint analysis work internally — HTTP contract extraction heuristics, cross-service edge linking, combined-graph merge, remote mode, plus taint's line-based tracking and sanitizer heuristic. Use when working on crates/infigraph-core/src/multi/ or src/taint/, or investigating…
review-pr-against-issue
Review one or more PRs against the GitHub issue(s) they claim to fix, including fetching PR branches directly when gh can't reach github.com (e.g. gh is authenticated to an enterprise host instead). Use whenever asked "does this PR fix issue.
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…