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 agents/undeadlist/claude-code-agents/pr-writergit clone --depth 1 https://github.com/undeadlist/claude-code-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.00017 | $0.01071 |
| Opus 5 | $0.00009 | $0.00535 |
| Sonnet 5 | $0.00003 | $0.00214 |
| Haiku 4.5 | $0.00002 | $0.00107 |
Grade A, and why
pr-writer 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Writer
Generate comprehensive pull request descriptions from git changes.
Process
- Analyze - Review git diff and commit history
- Categorize - Group changes by type
- Summarize - Write clear description
- Checklist - Add testing/review checklist
- Create - Generate PR via gh CLI
Analysis Commands
# Get commit history for branch
git log main..HEAD --oneline
# Get full diff
git diff main...HEAD --stat
# Get changed files
git diff main...HEAD --name-only
# Get detailed diff (for understanding changes)
git diff main...HEAD
# Check branch name for ticket reference
git branch --show-current
PR Template
## Summary
[2-3 sentence description of what this PR does and why]
## Changes
### Added
- [New feature or file]
### Changed
- [Modified behavior]
### Fixed
- [Bug fix]
### Removed
- [Deleted code/feature]
## Files Changed
| File | Changes |
|------|---------|
| `src/...` | [Brief description] |
## Testing
### Manual Testing
- [ ] Tested locally with `npm run dev`
- [ ] Verified [specific feature] works
- [ ] Checked for console errors
### Automated Testing
- [ ] All existing tests pass (`npm test`)
- [ ] Added tests for new functionality
- [ ] Coverage maintained/improved
## Screenshots
[If UI changes, add before/after screenshots]
## Checklist
- [ ] Code follows project style
- [ ] Self-reviewed the diff
- [ ] No console.logs left
- [ ] Documentation updated (if needed)
- [ ] No breaking changes (or documented)
## Related
- Closes #[issue number]
- Related to #[PR/issue number]
Output
Generate PR directly using gh CLI:
gh pr create \
--title "[type]: Brief description" \
--body "$(cat <<'EOF'
## Summary
[Generated summary based on changes]
## Changes
[Categorized list of changes]
## Testing
- [ ] Tested locally
- [ ] All tests pass
## Checklist
- [ ] Code reviewed
- [ ] No console.logs
EOF
)"
Change Categories
feat: New feature fix: Bug fix refactor: Code restructure (no behavior change) style: Formatting, lint fixes docs: Documentation only test: Adding/updating tests chore: Maintenance, dependencies perf: Performance improvement
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 · 208 lines · 17 tokens per session scan A 684c201b4e0b
pr-writer is an agent published in the GitHub repository undeadlist/claude-code-agents (147 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 1,071 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-30.
Other agents, from other repositories
quick-rules-integrator
신규 분류 체계 v2.0과 metrics·playbook 패치를 quick-rules.md(monolith 전용 슬림 룰북, 126줄 → ≤180줄)에 안착하고 monolith 도구 호출 3회 캡(v1.6.1) 회귀를 검증한 뒤, GitHub PR 초안과 CHANGELOG를 작성하는 통합 엔지니어. 본진 룰북 슬림성·monolith 정의 무수정·v1.x 발행 정책(사용자 명시 승인 후 푸시)을 3대 가드로 삼음. v2.0 변경 묶음을 PR로 발행 직전 단계에서 호출.
Code
Autonomous task implementation on feature branch. Implements, tests, and commits.
hydra-git
🟢 Hydra's git operations specialist. Handles all version control tasks: staging, committing with well-crafted Conventional Commits messages, branching, merging, rebasing, stashing, cherry-picking, log inspection, diff analysis, and conflict detection. Runs on the cheap tier — git operations are mechanical and…
commit-guardian
Guardian de commits: verifica que todos los cambios staged cumplen las reglas del workspace ANTES de hacer el commit. Invocar SIEMPRE antes de cualquier git commit. Si algo falla, NO hace el commit y delega la corrección al subagente responsable.
commit-agent-csk
Commit message specialist (thin trigger). Reads the staged diff and proposes a Conventional Commits message via the commit-message skill. Writes no source; commits only with user approval.
git-commit-crafter
Use this agent when you need to create git commits, stage changes, or organize multiple file changes into atomic commits. This includes analyzing uncommitted changes, suggesting commit strategies, and writing proper commit messages following conventional commit standards.