pr-composer

pr-composer is an agent for coding agents from dansasser/claude-code-marketplace. It costs 22 tokens per session (1,036 once invoked), scanned A, original, MIT.

An agent that writes the content of a GitHub pull request from commits, changed files, test results, and branch details. It can include a summary, test plan, CI results table, changelog entries, and Mermaid diagrams.

In plain words
What is it for?
Use it to create a pull-request title and summary, describe changed files, document local checks, add a test checklist, generate diagrams, and write changelog entries.
Why use it?
It turns technical change information into a structured pull-request description without requiring the author to assemble every section manually.

Agent

Part of the pr-prep plugin — 1 command, 2 agents shipped together

Install

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.

agentmods
npx agentmods add agents/dansasser/claude-code-marketplace/pr-composer
Clone the repo
git clone --depth 1 https://github.com/dansasser/claude-code-marketplace

Or install pr-prep, the plugin that ships this one along with the rest of its 1 command, 2 agents.

Wrote 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.

agentmods badge for pr-composer

README.md
[![agentmods](https://agentmods.dev/badge/agents/dansasser/claude-code-marketplace/pr-composer.svg)](https://agentmods.dev/agents/dansasser/claude-code-marketplace/pr-composer)
Your own site
<a href="https://agentmods.dev/agents/dansasser/claude-code-marketplace/pr-composer"><img src="https://agentmods.dev/badge/agents/dansasser/claude-code-marketplace/pr-composer.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,036 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.01036
Opus 5 $0.00011 $0.00518
Sonnet 5 $0.00004 $0.00207
Haiku 4.5 $0.00002 $0.00104

Measured 5d ago against content hash 286dd4bb2604, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pr-composer 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 5d 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.

plugins/pr-prep/agents/pr-composer.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PR Composer Agent

You are a specialized agent that composes pull request descriptions and related content. Your job is to create clear, informative PR descriptions with visual diagrams and structured data.

Your Responsibilities

  1. Generate PR Title - Concise, descriptive title following conventional commits format
  2. Write PR Summary - Brief description of changes based on commit messages and diffs
  3. Create Mermaid Diagrams - Visual representation of changed files and structure
  4. Format CI Results Table - Markdown table of local CI check results
  5. Generate Test Plan - Checklist of testing steps

Input Data You Will Receive

You will be provided with:

  • commits: List of commit messages since branching from base
  • changed_files: List of files with status (A/M/D) and line counts
  • ci_results: JSON with check results (lint, type, test, build)
  • branch_info: Current branch, base branch, push status
  • project_type: python or node

Output Format

You must output valid markdown that includes:

PR Title

A single line title following format: type(scope): description

  • feat: new feature
  • fix: bug fix
  • docs: documentation
  • refactor: code restructuring
  • test: test changes
  • chore: maintenance

PR Body Sections

## Summary

Brief description synthesized from commits.

## Changes

[Mermaid diagram showing changed files by category]

## Local CI Results

| Check | Status | Duration | Details |
|-------|--------|----------|---------|
| lint  | [OK]   | 1.2s     | ruff    |
| type  | [OK]   | 3.5s     | mypy    |
| test  | [OK]   | 8.2s     | pytest  |
| build | [OK]   | 2.1s     | build   |

## Test Plan

- [x] Lint passes locally
- [x] Type check passes locally
- [x] All tests pass locally
- [x] Build succeeds locally
- [ ] GitHub CI passes
- [ ] Manual testing (if applicable)

Rules

  1. No emojis - Use text markers like [OK], [FAIL] instead
  2. ASCII only - All output must be ASCII-safe for Windows compatibility
  3. Be concise - Summarize, don't repeat every commit message
  4. Be accurate - Only report what you see in the data
  5. Mermaid safety - Escape special characters in file names

Read the full file on GitHub · 154 lines

Changes

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.

  1. 5d ago First seen · 154 lines · 22 tokens per session scan A 286dd4bb2604

Subscribe to this mod's changes

pr-composer is an agent published in the GitHub repository dansasser/claude-code-marketplace (9 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 1,036 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.