A command that turns an internal PR/FAQ document and a CHANGELOG into a customer-facing press release for a chosen software release. A PR/FAQ is a planning document written before a product decision, while a CHANGELOG records shipped changes.

Use it to draft a press release for a specified version or, when no version is given, the latest released version in the CHANGELOG.

It helps align the public announcement with both the product narrative and what actually shipped, and stops when either required document or release version is missing.

externalize — Command by punt-labs

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/punt-labs/prfaq/externalize

Clone the repo

git clone --depth 1 https://github.com/punt-labs/prfaq

Per session 17 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,440 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.

Model	Per session	Once invoked
Fable 5	$0.00017	$0.01440
Opus 5	$0.00009	$0.00720
Sonnet 5	$0.00003	$0.00288
Haiku 4.5	$0.00002	$0.00144

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

Security

Grade A, and why

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

plugin/commands/externalize.md · 66 lines

How it starts

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

Externalize: PR/FAQ → Press Release

Convert the internal PR/FAQ decision document into a customer-facing press release for a specific release. The PR/FAQ is what the team debates; the press release is what the world reads.

Steps

Find the inputs. Read prfaq.tex (or the path the user specifies) and CHANGELOG.md from the project directory. Both are required — the PR/FAQ provides the narrative and the CHANGELOG provides what actually shipped. If either is missing, tell the user what's needed and stop.
Determine the target version. Three branches based on $ARGUMENTS:

a) Version specified — $ARGUMENTS contains a version string (e.g., v2.0, 2.0, 0.9.1): target that version's CHANGELOG entry. If the version doesn't exist in the CHANGELOG, tell the user and list available versions.

b) Empty — default to the latest version in the CHANGELOG (the topmost ## [X.Y.Z] entry that is not [Unreleased]). If the CHANGELOG has no versioned releases (only [Unreleased]), tell the user that externalize requires at least one versioned release and stop.

Detect the release type. Read the full CHANGELOG to understand the product's release history. The release type determines the tone, structure, and length of the press release:

Release type	Condition	Structure
First release	Target is the first (or only) version in the CHANGELOG	Full press release: headline, lede, problem, solution, customer quote, getting started, spokesperson quote, CTA, boilerplate
Major update	Target has a major version bump from the prior release (e.g., v1.x → v2.0) and prior versions exist	Update announcement: headline focuses on "what's new", lede highlights why this upgrade matters, "What's New" section replaces "Problem", solution focused on new capabilities, CTA includes upgrade path
Minor/patch	Target is a minor or patch bump (e.g., v1.0 → v1.1 or v1.0.1)	Short release note: headline, lede summarizing improvements, key changes list, availability, boilerplate

Read the full file on GitHub · 66 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.

2d ago First seen · 66 lines · 17 tokens per session scan A fc83f5f8b9fc

Subscribe to this mod's changes

externalize is a command published in the GitHub repository punt-labs/prfaq (25 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 1,440 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-30.

Documents Git and workflow LaTeX Planning beta claude-code-plugin pdf-generation product-discovery

externalize

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Externalize: PR/FAQ → Press Release

Steps

What this file has done since we first saw it

Other commands, from other repositories

oracle-dev

refine-dev

refine

contracts-dev

prove-dev

prove