pr-message

A command that writes a pull-request description to a Markdown file. A pull request is a proposed set of code changes for review before it is merged.

In plain words
What is it for?
Use it to document what changed, why non-obvious decisions were made, real challenges, testing, and breaking changes. It writes the result to pr-description.md at the repository root.
Why use it?
It turns the branch's commits and actual differences into a description that can be pasted into a code-hosting service without losing formatting.

Command

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 commands/missingpackage/nightshift/pr-message
Clone the repo
git clone --depth 1 https://github.com/MissingPackage/nightshift
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 225 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.00018 $0.00225
Opus 5 $0.00009 $0.00112
Sonnet 5 $0.00004 $0.00045
Haiku 4.5 $0.00002 $0.00022

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

Security

Grade A, and why

pr-message 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.

commands/pr-message.md · 19 lines

What it actually says

Analyze every commit on this branch versus its base (default: dev) and write the PR description to pr-description.md at the repo root — a FILE, because chat formatting dies on paste (the "me lo scrivi in un md?" ritual, automated).

Structure: Summary (3 bullets max) · What changed (grouped by area, with the why for each non-obvious choice) · Challenges & how they were resolved (only real ones) · Test plan (checkboxes: what was run with results, what the reviewer should run) · Breaking changes / migrations (or "none").

Rules: derive from the actual diff and commit history, not from memory of the session; no AI attribution anywhere; if the branch mixes unrelated work, say so at the top and recommend the split rather than papering over it. End by printing only the file path and the Summary bullets.

$ARGUMENTS

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 · 19 lines · 18 tokens per session scan A fe8c33148796

Subscribe to this mod's changes

pr-message is a command published in the GitHub repository MissingPackage/nightshift (2 stars, last pushed 16d ago), licensed MIT. It adds 18 tokens to every session and 225 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.