agentmods.dev

issue-approve

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

A command that approves the active DSSE issue and changes its status from open to in-progress. Approval is the point where the planned implementation is authorized to begin.

In plain words
What is it for?
Use it after approving an issue plan, then begin changes only within its allowed files and continue with verification, review, and closeout.
Why use it?
It prevents work from starting before the plan is signed off and activates the workflow’s stop-time control.

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 14 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-approve
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-approve

README.md
[![agentmods](https://agentmods.dev/badge/commands/assafkip/prd-os/issue-approve.svg)](https://agentmods.dev/commands/assafkip/prd-os/issue-approve)
Your own site
<a href="https://agentmods.dev/commands/assafkip/prd-os/issue-approve"><img src="https://agentmods.dev/badge/commands/assafkip/prd-os/issue-approve.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 239 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.00014 $0.00239
Opus 5 $0.00007 $0.00120
Sonnet 5 $0.00003 $0.00048
Haiku 4.5 $0.00001 $0.00024

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

Security

Grade A, and why

issue-approve 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 5d 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-approve.md · 17 lines

What it actually says

Approve the active DSSE issue after the founder has signed off on the plan. Execute in order:

  1. Run python3 "${CLAUDE_PLUGIN_ROOT}/scripts/issue_runner.py" approve. This reads the active issue spec, confirms its status is currently open, and flips it to in-progress. The command writes the spec directly — do not use the Edit tool for this.

  2. If approve exits non-zero:

    • No active issue: tell the founder to run /issue-start <issue-id> first.
    • Status already in-progress: safe to proceed, the runner is idempotent on re-approval.
    • Any other error: report it verbatim. Do not edit the spec manually to work around it.

  3. Confirm in one line: "Issue $ISSUE_ID is now in-progress. Stop-time gate is armed."

After approval, proceed with the first concrete change from the plan. All edits must target allowed_files. Normal DSSE flow resumes: /issue-verify, /issue-review, /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. 5d ago First seen · 17 lines · 14 tokens per session scan A 62ad9554f1a3

Subscribe to this mod's changes

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

Project managementai-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

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

adr

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

AInsteinsBR/renata · 24 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

hypothesis-check

Confronts each PRD hypothesis with the real measured number, forces an explicit verdict, and triggers a concrete action.

AInsteinsBR/renata · 24 tokens