pr-creation

A rule for creating GitHub pull requests through a designated workflow with a clear title and detailed review information. GitHub is a service for hosting code and reviewing proposed changes.

In plain words
What is it for?
Use it when opening or editing pull requests to include the problem, solution, behavior changes, files, risks, rollout, and test plan.
Why use it?
It keeps pull requests understandable to reviewers and prevents internal task IDs or agent details from appearing in the public request.

Cursor rule

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/david405/harness-kit/pr-creation
Clone the repo
git clone --depth 1 https://github.com/David405/harness-kit
Per session 225 This file is loaded in full into every session.
When invoked 225 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.00225 $0.00225
Opus 5 $0.00112 $0.00112
Sonnet 5 $0.00045 $0.00045
Haiku 4.5 $0.00022 $0.00022

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

Security

Grade A, and why

pr-creation 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 yesterday.

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.

rules/pr-creation.mdc · 21 lines

What it actually says

Pull request creation

When opening or editing a GitHub PR, read and follow the create-pull-request skill (.agents/skills/create-pull-request/SKILL.md).

Quick rules

  • Title: type(scope): plain English — no feature ledger IDs, audit codes, or contract paths.
  • Body: full template in the skill — Summary, Problem, Solution, Behaviour changes, Files changed, Risk and rollout, Test plan. Enough detail for a reviewer who was not in the session.
  • Keep local: contracts, FEATURES.json IDs, harness-review output, PENDING_REVIEW — chat only.
  • Never: tool attribution (Made with Cursor, Co-Authored-By assistant) in title, body, or commits.

Harness review runs before the PR; its output goes to the human in chat, not on GitHub.

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. yesterday First seen · 21 lines · 225 tokens per session scan A 2e7ae42e428c

Subscribe to this mod's changes

pr-creation is a cursor rule published in the GitHub repository David405/harness-kit (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 225 tokens to every session, about $0.0011 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.