agentmods.dev

vote

vote is a command for coding agents from punt-labs/prfaq. It costs 16 tokens per session (3,679 once invoked), scanned A, original, MIT.

A structured go/no-go assessment of a PR/FAQ, a document that explains a proposed product and answers expected questions. It evaluates the customer problem, the proposed solution, and whether to act now.

In plain words
What is it for?
Use it to decide whether a product idea is worth pursuing, whether its solution is differentiated and feasible, and whether its timing makes sense.
Why use it?
It turns the document’s evidence, risks, citations, scope, and alternatives into a clear decision instead of an informal discussion.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the prfaq-dev plugin — 1 skill, 14 commands, 8 agents, 1 hook shipped together

not rated 25 4d ago A scan 16 tokens original MIT
View the source file punt-labs/prfaq
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/vote
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.

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.

agentmods badge for vote

README.md
[![agentmods](https://agentmods.dev/badge/commands/punt-labs/prfaq/vote.svg)](https://agentmods.dev/commands/punt-labs/prfaq/vote)
Your own site
<a href="https://agentmods.dev/commands/punt-labs/prfaq/vote"><img src="https://agentmods.dev/badge/commands/punt-labs/prfaq/vote.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,679 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.00016 $0.03679
Opus 5 $0.00008 $0.01840
Sonnet 5 $0.00003 $0.00736
Haiku 4.5 $0.00002 $0.00368

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

Security

Grade A, and why

vote 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 4d 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/vote.md · 209 lines

How it starts

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

Go/No-Go Decision: PR/FAQ Vote

Synthesize the PR/FAQ into a structured go/no-go recommendation across three decision gates. The vote reads the document's own evidence — risk ratings, FAQs, citations, feature scope — and renders a binary verdict. This is the decision; /prfaq:meeting is the deliberation.

Decision Gates

The three gates map to Cagan's four risks, reframed as actionable questions:

Gate Question Risks Key Sections
Gate 1 Is this a customer problem worth solving? Value + Viability Problem, Customer Evidence FAQ, TAM FAQ, Revenue Model FAQ, P&L FAQ, Risk Assessment (value + viability ratings)
Gate 2 Do we have a differentiated solution? Usability + Feasibility Solution, Getting Started, Competitive Landscape FAQ, Technical FAQs, Dependencies FAQ, Risk Assessment (usability + feasibility ratings)
Gate 3 Should we do this now? Opportunity cost "Best alternatives" FAQ, Feature Appendix scope, "Why now?" FAQ, meeting decisions (if available)

Gate 1 is a hard prerequisite. A NO-GO on Gate 1 makes the overall verdict NO-GO regardless of Gates 2 and 3. Gates 2 and 3 are still assessed for informational purposes — even a NO-GO project has lessons worth recording.

Steps

  1. Find the document(s). Two modes:

    Single-document mode — $ARGUMENTS is empty or specifies one path. If empty, search for prfaq.tex in the project root using Glob. If not found, tell the user to run /prfaq first.

    Multi-document mode — $ARGUMENTS contains two or more .tex file paths. Verify each exists. If any is missing, report which ones and stop.

  2. Read reference guides. Load the evaluation criteria from:

    • ${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/four-risks.md — risk signals (low/high) for each of the four risks
    • ${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/unit-economics.md — viability metrics and what to look for
    • ${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/decision-quality.md — cognitive biases that distort decision-making

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

  1. 4d ago First seen · 209 lines · 16 tokens per session scan A 2a03b10ab201

Subscribe to this mod's changes

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

LaTeXMarketing and SEOPlanningbetaclaude-code-pluginpdf-generationproduct-discovery
Related

Other commands, from other repositories

oracle-dev

Generate property-based test harness using Lean 4 model as oracle.

punt-labs/z-spec · 12 tokens

refine-dev

Verify code refines Z specification via abstraction function and commutativity checks.

punt-labs/z-spec · 14 tokens

refine

Verify code refines Z specification via abstraction function and commutativity checks.

punt-labs/z-spec · 14 tokens

contracts-dev

Generate runtime contracts (preconditions, postconditions, invariants) from a Z specification.

punt-labs/z-spec · 17 tokens

code2model-dev

Create a Z specification for stateful entities in a system.

punt-labs/z-spec · 11 tokens

partition-dev

Derive test cases from Z specification using TTF testing tactics.

punt-labs/z-spec · 12 tokens