A command that turns an existing document into a PR/FAQ, a planning document containing a proposed announcement and questions with answers. It extracts the document's ideas and fills every section.

Use it with a Markdown, text, or PDF file—or pasted text—to create a complete PR/FAQ and start the full generation workflow.

It removes the need to copy information manually or start a PR/FAQ from an empty template.

import — 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/import

Clone the repo

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

Or install prfaq-dev, the plugin that ships this one along with the rest of its 1 skill, 14 commands, 8 agents, 1 hook.

Per session 15 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,111 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.00015	$0.01111
Opus 5	$0.00008	$0.00556
Sonnet 5	$0.00003	$0.00222
Haiku 4.5	$0.00002	$0.00111

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

Security

Grade A, and why

import 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 3d 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/import.md · 70 lines

How it starts

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

Import Document into PR/FAQ

Convert an existing document — any format, any structure — into a complete PR/FAQ. The import parses the source document, extracts ideas, maps them to PR/FAQ sections, and then launches the full /prfaq generation workflow with that content as a head start. Every section gets generated — nothing is left as a placeholder.

Steps

Determine the input. Three branches based on $ARGUMENTS:

a) File path — $ARGUMENTS ends in .md, .txt, or .pdf and the file exists: read the file using the Read tool. For PDFs, the Read tool handles them natively.

b) Text — $ARGUMENTS is non-empty but not a file path: treat it as the document content directly.

c) Empty — $ARGUMENTS is empty: ask the user via AskUserQuestion:
- Paste content — user will paste the document as their next message
- Provide a file path — user will give a path to read
- Cancel
If the user chooses to paste, wait for their next message and use that as the document content.
Check for existing PR/FAQ. Use Glob to search for prfaq.tex in the project root. If found, ask via AskUserQuestion:
- Overwrite — replace the existing document with the import
- Save as new file — ask the user for a filename (default: prfaq-imported.tex)
- Cancel
Remember the chosen output path for step 5.

Extract and map content. Read the input document and identify content that maps to the /prfaq discovery questions:

Discovery Input	Look for in source document
Stage	Product maturity indicators — whether users exist, launch status, evidence level (hypothesis / validated / growth)
Customer	Target user, persona, role, audience, market segment
Problem	Pain points, challenges, current state, workarounds
Solution	Product description, approach, how it works, key features
Differentiation	Competitive advantage, unique insight, why this is better
Market	TAM, market size, demand signals, growth trends
Risks	Assumptions, unknowns, dependencies, what could go wrong

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

3d ago First seen · 70 lines · 15 tokens per session scan A 97593141c665

Subscribe to this mod's changes

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

LaTeX Planning Writing and docs beta claude-code-plugin pdf-generation product-discovery

import

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Import Document into PR/FAQ

Steps

What this file has done since we first saw it

Other commands, from other repositories

oracle-dev

refine-dev

refine

contracts-dev

code2model-dev

partition-dev