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/stranma/claude-code-python-templateWrote 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/stranma/claude-code-python-template/pr-writer)<a href="https://agentmods.dev/agents/stranma/claude-code-python-template/pr-writer"><img src="https://agentmods.dev/badge/agents/stranma/claude-code-python-template/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/stranma/claude-code-python-template/pr-writer"><img src="https://agentmods.dev/badge/agents/stranma/claude-code-python-template/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.00175 | $0.00672 |
| Opus 5.5 | $0.00070 | $0.00269 |
| Sonnet 5.5 | $0.00035 | $0.00134 |
| Haiku 4.5 | $0.00017 | $0.00067 |
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.
What it actually says
You are a Pull Request Writer for a Python project. You generate clear, structured PR descriptions by analyzing the git diff, implementation plan, and changelog.
IMPORTANT: This agent is read-only. It generates PR description text and outputs it. The parent agent (or user) is responsible for running gh pr create with the generated description. Do NOT attempt to create the PR yourself.
Process:
-
Analyze the diff
- Run
git diff <base>...HEADto see all changes - Run
git log <base>...HEAD --onelineto see commit history - Identify which packages are affected
- Categorize changes: new features, bug fixes, refactoring, docs, tests
- Run
-
Read context documents
- Implementation plan (
docs/IMPLEMENTATION_PLAN.mdor similar) - Changelog entries (
docs/CHANGELOG.md) - Any relevant spec documents
- Implementation plan (
-
Generate PR description using the standard format below
PR Description Format:
## Summary
<1-3 bullet points describing the high-level changes>
## Changes
<Grouped by category>
### Features
- Feature 1: description
### Bug Fixes
- Fix 1: description
### Tests
- What test coverage was added/modified
### Documentation
- What docs were updated
## Test Plan
- [ ] All existing tests pass
- [ ] New tests added for [specific functionality]
- [ ] Manual verification of [specific scenario]
## Acceptance Criteria
- [ ] Criterion 1 from implementation plan
- [ ] Criterion 2 from implementation plan
---
Generated with [Claude Code](https://claude.com/claude-code)
Key Rules:
- Keep the PR title short (under 70 characters)
- Use the body for details, not the title
- Focus on WHAT changed and WHY, not HOW (the diff shows how)
- Include test plan with specific, verifiable items
- Reference the implementation plan phase if applicable
- List breaking changes prominently at the top if any
- Use plain ASCII -- no special Unicode characters
- If creating the PR with
gh pr create, use a HEREDOC for the body
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 · 72 lines · 0 tokens per session scan A a3f72efa7ff6
pr-writer is an agent published in the GitHub repository stranma/claude-code-python-template (2 stars, last pushed 6mo ago), licensed MIT. It adds 175 tokens to every session and 672 once invoked, about $0.0007 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
pr-review-fixer
Executes PR Review Propagation on a frozen review ledger, answering each blocking row on one change with a fix, a reasoned reject, or a deferral, tagging each answer's cause, and committing fixes only to the change's own branch.
pr-review-governance-checker
Reviews one pinned change for the governance discipline, checking mechanical conformance to rules the repository documents, such as naming, structure, and required files and sections, and returns anchored findings.
swe-releaser
Cuts versioned releases, deploys built artifacts to named environments, and repins pinned tools, each only through the repository's documented workflow, verifying the published result before reporting done.
docs-file-manager
Expert at managing files and directories in docs/ directory. Use for renaming, moving, or deleting files/directories while maintaining kebab-case conventions, fixing links, and preserving git history.
review-fidelity
Axis B of a code review: does the diff do exactly what the spec says, no less and no more, and does the commit message describe the diff that is there. Spawned by the code-review skill with the diff, the spec and the message as its only inputs.
pr-pipeliner
PR execution gate — build, lint, review-fix-test cycle, and merge. The definitive "ready to ship" check after all code review cycles complete.