prd-build-status

prd-build-status is a skill for Claude Code from sjarmak/agent-workflows. It costs 11 tokens per session (335 once invoked), scanned B, original, MIT.

A status command for a product requirements document (PRD) build, where a PRD describes what a product or feature should do.

In plain words
What is it for?
Use it to view the current pass, work units by dependency layer, overall progress, and recent activity from the build log.
Why use it?
It shows whether the build is active, paused, or finished and makes unfinished, failed, and completed work visible.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the agent-workflows plugin — 28 skills, 4 agents, 4 hooks shipped together

Good fit Use it to view the current pass, work units by dependency layer, overall progress, and recent activity from the build log.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sjarmak/agent-workflows/prd-build-status
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.

Any agent
npx skills add sjarmak/agent-workflows --skill prd-build-status
Clone the repo
git clone --depth 1 https://github.com/sjarmak/agent-workflows

Made for: Claude Code.

Or install agent-workflows, the plugin that ships this one along with the rest of its 28 skills, 4 agents, 4 hooks.

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 prd-build-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/sjarmak/agent-workflows/prd-build-status.svg)](https://agentmods.dev/skills/sjarmak/agent-workflows/prd-build-status)
Your own site
<a href="https://agentmods.dev/skills/sjarmak/agent-workflows/prd-build-status"><img src="https://agentmods.dev/badge/skills/sjarmak/agent-workflows/prd-build-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 335 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00011 $0.00335
Opus 5 $0.00005 $0.00168
Sonnet 5 $0.00002 $0.00067
Haiku 4.5 $0.00001 $0.00034

Measured 7d ago against content hash 3fe3cc0ce1f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade B, and why

prd-build-status scanned grade B with 1 finding 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 7d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat .claude/prd-build.state.json
skills/prd-build-status/SKILL.md · 48 lines

What it actually says

PRD Build Status

Read the state file and present a clear status report.

if [ -f .claude/prd-build.state.json ]; then
  cat .claude/prd-build.state.json
else
  echo "NO_STATE_FILE"
fi

If NO_STATE_FILE: tell the user there's no active PRD build run. Suggest /prd-build <prd-path> to start one.

Otherwise, also read .claude/prd-build-artifacts/dag.json with the Read tool to get unit-level detail.

Status Report Format

PRD Build Status: <status>
Pass: <current>/<max> | Started: <time>

Progress:
  Layer 0: [landed] unit-a, [landed] unit-b
  Layer 1: [active] unit-c (implement), [pending] unit-d
  Layer 2: [pending] unit-e

Summary: X/Y units landed | Z active | W pending | E evicted

Use status indicators:

  • landed — merged to integration branch
  • active — agent currently working (show pipeline stage if available)
  • passed — done, waiting in merge queue
  • pending — not yet started
  • evicted — merge failed, awaiting retry
  • failed — permanently failed

Also read and show the last 10 lines of .claude/prd-build.log.md as recent activity.

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. 7d ago First seen · 48 lines · 11 tokens per session scan B 3fe3cc0ce1f2

Subscribe to this mod's changes

prd-build-status is a skill published in the GitHub repository sjarmak/agent-workflows (9 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 335 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.