pr-template

A standard template for writing pull request descriptions. A pull request is a proposed code change that others review before it is merged into a project.

In plain words
What is it for?
Use it when preparing a pull request summary, ticket reference, test URLs, environments, verification steps, before-and-after behavior, and possible regressions.
Why use it?
A consistent description makes it easier for reviewers to understand what changed, how to test it, which ticket it addresses, and what might regress.

Cursor rule for Cursor

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 rules/adobecom/express-milo/pr-template
Clone the repo
git clone --depth 1 https://github.com/adobecom/express-milo

Made for: Cursor.

Per session 247 This file is loaded in full into every session.
When invoked 247 The same file — it is already loaded in full.
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.00247 $0.00247
Opus 5 $0.00123 $0.00123
Sonnet 5 $0.00049 $0.00049
Haiku 4.5 $0.00025 $0.00025

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

Security

Grade A, and why

pr-template 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 2d 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.

.cursor/rules/pr-template.mdc · 46 lines

What it actually says

When asked to make a PR description, use the following template and use any links provided as needed.

Summary

Briefly describe the features or fixes introduced in this PR.


Jira Ticket

Resolves: MWPW-NUMBER


Test URLs

Env URL
Before https://main--express-milo--adobecom.aem.page/express/
After https://--express-milo--adobecom.aem.page/express/?martech=off

Verification Steps

  • Steps to reproduce the issue or view the new feature.
  • What to expect before and after the change.

Potential Regressions

  • https://--express-milo--adobecom.aem.live/express/?martech=off

Additional Notes

(If applicable) Add context, related PRs, or known issues here.

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. 2d ago First seen · 46 lines · 247 tokens per session scan A 5acb94a4e4ac

Subscribe to this mod's changes

pr-template is a cursor rule published in the GitHub repository adobecom/express-milo (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 247 tokens to every session, about $0.0012 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.