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.
git clone --depth 1 https://github.com/stuartshields/claude-setupWrote 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/agents/stuartshields/claude-setup/pr-writer)<a href="https://agentmods.dev/agents/stuartshields/claude-setup/pr-writer"><img src="https://agentmods.dev/badge/agents/stuartshields/claude-setup/pr-writer/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/agents/stuartshields/claude-setup/pr-writer"><img src="https://agentmods.dev/badge/agents/stuartshields/claude-setup/pr-writer.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.00042 | $0.00701 |
| Opus 5.5 | $0.00017 | $0.00280 |
| Sonnet 5.5 | $0.00008 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
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 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Writer
Generate structured pull request descriptions from git diff analysis.
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 stats
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
- [ ] Verified [specific feature] works
- [ ] Checked for errors
### Automated Testing
- [ ] All existing tests pass
- [ ] 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 debug logging 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'
[generated content]
EOF
)"
Change Categories
| Prefix | Meaning |
|---|---|
| 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.
- 1mo ago First seen · 133 lines · 42 tokens per session scan A 0c9d2f236188
pr-writer is an agent published in the GitHub repository stuartshields/claude-setup (2 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 701 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 agents, from other repositories
commit-detector
Use PROACTIVELY when: user says commit/save/git, mentions wip/feat/fix/chore. Do NOT use for: code review, non-commit git ops (log/diff/status).
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
cover-letter-writer
Writes a tailored LaTeX cover letter using job analysis and resume summary. Follows strict anti-echo rules — no mirroring the job post, no filler, plain English at the user's configured level. Saves {fileprefix}coverletter.tex to the output folder.
resume-tailor
Tailors the candidate's resume LaTeX file to a specific job using masterdata.yaml and job analysis output. Selects relevant bullets, reorders skills, and weaves in ATS keywords. Saves {fileprefix}resume.tex to the output folder.
pr-standards
Git Commit & PR Standards for AI-Assisted Development.
job-analyzer
Extracts structured info from a job post — company name, job title, job type, key skills, ATS keywords, responsibilities, and address. Always run this first before resume or cover letter agents.