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 shwilliamson/automatasaurus --skill pr-writinggit clone --depth 1 https://github.com/shwilliamson/automatasaurusWrote 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/shwilliamson/automatasaurus/pr-writing)<a href="https://agentmods.dev/skills/shwilliamson/automatasaurus/pr-writing"><img src="https://agentmods.dev/badge/skills/shwilliamson/automatasaurus/pr-writing.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.1 | $0.00028 | $0.01544 |
| Opus 5 | $0.00014 | $0.00772 |
| Sonnet 5 | $0.00006 | $0.00309 |
| Haiku 4.5 | $0.00003 | $0.00154 |
Grade A, and why
pr-writing 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 8d 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Writing Skill
Guidelines for writing pull request descriptions that help reviewers understand and approve changes quickly.
Creating PRs (Sandbox Compatibility)
Don't use heredocs (<<EOF) with gh pr create - they fail in sandboxed environments.
Use the Write tool + --body-file pattern:
# 1. Use Write tool to create .github-pr-body.md with your PR body
# 2. Create the PR
gh pr create --title "#42 feat: Add user auth" --body-file .github-pr-body.md
# 3. Clean up
rm .github-pr-body.md
PR Title Format
#<issue-number> <type>: <concise description>
Always prefix the PR title with the GitHub issue number to enable easy cross-referencing.
Types
| Type | Use For |
|---|---|
feat |
New feature or functionality |
fix |
Bug fix |
refactor |
Code restructuring without behavior change |
docs |
Documentation only |
test |
Adding or updating tests |
chore |
Build, tooling, dependencies |
perf |
Performance improvement |
style |
Formatting, whitespace (no logic change) |
Good Titles
#42 feat: Add user registration endpoint
#187 fix: Prevent duplicate form submissions
#23 refactor: Extract authentication logic into service
#91 docs: Add API documentation for user endpoints
Bad Titles
Update code # Too vague, no issue number
Fixed the bug # Which bug? No issue number
WIP # Not ready for review
feat: Add login # Missing issue number prefix
PR Body Structure
## Summary
[1-3 sentences explaining WHAT changed and WHY]
Closes #<issue-number>
## Changes
- [Specific change 1]
- [Specific change 2]
- [Specific change 3]
## Testing
- [ ] Unit tests added/updated
- [ ] Integration tests pass
- [ ] Manual testing completed
## Screenshots (if UI changes)
[Before/after screenshots or GIFs]
## Notes for Reviewers
[Optional: Areas to focus on, known limitations, questions]
Writing the Summary
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.
- 8d ago First seen · 274 lines · 28 tokens per session scan A f46a857cb41e
pr-writing is a skill published in the GitHub repository shwilliamson/automatasaurus (5 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 1,544 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…