agentmods.dev

issue-verify

issue-verify is a command for coding agents from assafkip/prd-os. It costs 13 tokens per session (303 once invoked), scanned A, original, MIT.

A command runs every verification check required by the active issue and records a verified receipt only when all checks pass.

In plain words
What is it for?
It checks the active issue, reports each command and failure output, and marks the issue verified after successful completion.
Why use it?
It prevents an issue from being marked verified when a required check fails or no issue has been loaded.

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 prd-os plugin — 1 skill, 14 commands shipped together

not rated 10 2mo ago A scan 13 tokens original MIT
View the source file assafkip/prd-os
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/assafkip/prd-os/issue-verify
Clone the repo
git clone --depth 1 https://github.com/assafkip/prd-os

Or install prd-os, the plugin that ships this one along with the rest of its 1 skill, 14 commands.

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 issue-verify

README.md
[![agentmods](https://agentmods.dev/badge/commands/assafkip/prd-os/issue-verify.svg)](https://agentmods.dev/commands/assafkip/prd-os/issue-verify)
Your own site
<a href="https://agentmods.dev/commands/assafkip/prd-os/issue-verify"><img src="https://agentmods.dev/badge/commands/assafkip/prd-os/issue-verify.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 303 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.00013 $0.00303
Opus 5 $0.00006 $0.00151
Sonnet 5 $0.00003 $0.00061
Haiku 4.5 $0.00001 $0.00030

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

Security

Grade A, and why

issue-verify 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.

plugins/prd-os/commands/issue-verify.md · 28 lines

What it actually says

Verify the active DSSE issue. Execute in order:

  1. Run python3 "${CLAUDE_PLUGIN_ROOT}/scripts/issue_runner.py" status. Confirm an issue is loaded. If issue_id is null, stop and tell the founder to run /issue-start <issue-id> first.

  2. Read the spec's required_checks list (already in the status output's loaded spec, or re-load the spec file directly).

  3. Run every check in the list, one at a time, from the repo root. For each:

    • Echo the command before running.
    • Run it via Bash.
    • Capture exit code and the last ~20 lines of output.

  4. If every check exits 0:

    • Run python3 "${CLAUDE_PLUGIN_ROOT}/scripts/issue_runner.py" mark verified.
    • Report: "verified receipt recorded at ."
    • List the checks that ran, one per line.

  5. If any check fails:

    • Do NOT call mark verified.
    • Report which check failed, its exit code, and the relevant output.
    • Stop. Do not attempt to fix silently. Tell the founder.

Do not run /codex:review here. That is /issue-review. Do not edit the spec here. That happens only in /issue-start and /issue-closeout.

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. 3d ago First seen · 28 lines · 13 tokens per session scan A c4dded133b15

Subscribe to this mod's changes

issue-verify is a command published in the GitHub repository assafkip/prd-os (10 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 303 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.

Testingai-workflowclaude-codefounder-toolsprdproduct-management
Related

Other commands, from other repositories

plan-phase

Wraps superpowers:writing-plans with RENATA guardrails to produce a method-compliant, ADR-respecting execution plan reviewed by the architect.

AInsteinsBR/renata · 30 tokens

adopt

Adopts RENATA in an existing codebase — reverse-engineers the technical pattern, feature inventory, as-built specs and a retroactive PRD, confirming every item with you.

AInsteinsBR/renata · 36 tokens

adr

Formalizes an ADR from a technical decision using the Nygard format and syncs its enforcement block in rules.yaml.

AInsteinsBR/renata · 24 tokens

screens

Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.

AInsteinsBR/renata · 27 tokens

assumption-test

Surfaces the riskiest business assumption behind the PRD and designs the cheapest test to falsify it before building.

AInsteinsBR/renata · 24 tokens

bug-report

Converts a raw bug report from production into a structured, severity-classified item and routes it to the right next step.

AInsteinsBR/renata · 25 tokens