agentmods.dev

issue-start

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

A command that loads a DSSE issue specification and prepares the agent to work on it. The specification defines the allowed files, required checks, and required reviews.

In plain words
What is it for?
Loading an issue, presenting its constraints and checks, and preparing the first implementation step.
Why use it?
It makes the agent follow the issue's approved boundaries and waits for the founder to approve the work plan before editing.

Command

Part of the prd-os plugin — 1 skill, 14 commands shipped together

10 2mo ago A scan 10 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-start
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.

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 407 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.00010 $0.00407
Opus 5 $0.00005 $0.00204
Sonnet 5 $0.00002 $0.00081
Haiku 4.5 $0.00001 $0.00041

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

Security

Grade A, and why

issue-start 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-start.md · 30 lines

What it actually says

You are starting a DSSE issue. The issue id is: $ARGUMENTS

Execute the following, in order:

  1. Run python3 "${CLAUDE_PLUGIN_ROOT}/scripts/issue_runner.py" load $ARGUMENTS. The output is JSON describing the loaded spec. If the command exits non-zero, stop and report the error. Do not invent an issue spec.

  2. Read the full spec file at the spec_path returned by step 1.

  3. Present a plan to the founder:

    • One line summarizing the title and priority.
    • The full allowed_files list exactly as loaded. State explicitly: "all edits must target one of these paths."
    • The full required_checks list. State: "these must all exit 0 before /issue-verify will record the verified receipt."
    • The full required_reviews list.
    • The first concrete change you plan to make, in one sentence.

  4. Wait for the founder to approve the plan or redirect. Do not flip the spec status and do not start editing until they confirm.

  5. On approval, run /issue-approve. That command flips the spec status from open to in-progress and arms the stop-time gate. Planning before this step is intentionally gate-exempt so a loaded spec does not spam the Stop hook while the plan is being reviewed.

Rules while the issue is loaded:

  • Every edit you make must target a path that matches allowed_files.
  • The PreToolUse scope hook will block out-of-scope edits automatically.
  • Do not mark the issue verified, reviewed, or closed yourself. Use /issue-verify, /issue-review, /issue-closeout.
  • If you discover mid-issue that the scope is wrong, update the spec file's allowed_files first, explain why, then continue.
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 · 30 lines · 10 tokens per session scan A 3f86a8f5d10b

Subscribe to this mod's changes

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

PlanningProject 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

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