A pull-request writing rule for the SAGE workflow. A pull request is a proposed code change submitted for review before it is merged.

Use it to create a PR title and description from spec.md, behavior.md, code files, and optionally doc.md, including decisions, testing, and out-of-scope work.

It turns project notes and completed code into a consistent review description without requiring you to write it from scratch.

sage-pr — Cursor rule for Cursor by gustavobarbosab/sage

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.

Clone the repo

git clone --depth 1 https://github.com/gustavobarbosab/sage

Made for: Cursor.

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/gustavobarbosab/sage/sage-pr/github.svg)](https://agentmods.dev/rules/gustavobarbosab/sage/sage-pr)

Your own site

<a href="https://agentmods.dev/rules/gustavobarbosab/sage/sage-pr"><img src="https://agentmods.dev/badge/rules/gustavobarbosab/sage/sage-pr/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/gustavobarbosab/sage/sage-pr"><img src="https://agentmods.dev/badge/rules/gustavobarbosab/sage/sage-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 382 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00013	$0.00382
Opus 5.5	$0.00005	$0.00153
Sonnet 5.5	$0.00003	$0.00076
Haiku 4.5	$0.00001	$0.00038

Measured 2mo ago against content hash 69560cf35e71, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sage-pr 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 2mo 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.

skill/cursor/.cursor/rules/sage-pr.mdc · 69 lines

What it actually says

/sage pr

Generates pr.md — a ready-to-paste PR title and description with ADR-style decisions.

Instructions

Read:

spec.md
behavior.md
The generated code files
doc.md if it exists

Generate pr.md with this structure:

## <Short imperative title — under 72 chars>

<2–3 sentence summary of what this PR implements and why.>

### Changes
- <Concrete code change 1>
- <Concrete code change 2>
- <Concrete code change 3>

### Decisions (ADR-style)
- <Decision made during behavior step>
  → <The reasoning behind it>
- <Another decision>
  → <The reasoning>

### Acceptance criteria covered
- [x] <Item from spec.md>
- [x] <Item from spec.md>

### Out of scope
- <What this PR deliberately does NOT include>

### Testing
- <Scenarios from behavior.md that are covered>
- <What was tested manually>

Rules

Title must be imperative voice ("Implement login screen" not "Implemented")
Title must be under 72 characters
Every resolved open question from behavior.md becomes a "Decision" entry with its reasoning
Do not include implementation details that belong in code review comments

After generation

Tell the user: "pr.md is ready. To open the PR directly from terminal:

gh pr create \
  --title \"$(head -n1 pr.md | sed 's/^## //')\" \
  --body \"$(tail -n +2 pr.md)\"

Run /sage doc to also generate the behavioral reference documentation."

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.

2mo ago First seen · 69 lines · 13 tokens per session scan A 69560cf35e71

Subscribe to this mod's changes

sage-pr is a cursor rule published in the GitHub repository gustavobarbosab/sage (2 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 382 once invoked, about $0.0001 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.

Git and workflow

sage-pr

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

/sage pr

Instructions

Rules

After generation

What this file has done since we first saw it

Other cursor rules, from other repositories

rebase-only-merged-agents

iris

git-workflow

release-checklist

git-workflow

branching-merging-strategy