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.
npx skills add jpoutrin/product-forge --skill prd-statusgit clone --depth 1 https://github.com/jpoutrin/product-forgeWrote 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.
[](https://agentmods.dev/skills/jpoutrin/product-forge/prd-status)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/prd-status"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/prd-status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/prd-status"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/prd-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00011 | $0.00945 |
| Opus 5.5 | $0.00004 | $0.00378 |
| Sonnet 5.5 | $0.00002 | $0.00189 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade B, and why
prd-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 1mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- If no write permissions: Report error and suggest using sudo ## Example How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prd-status
Category: Product & Strategy
Usage
prd-status <prd-file> <new-status> [--comment "reason for change"]
Arguments
<prd-file>: Required - Path to the PRD file to update<new-status>: Required - New status (draft, review, approved, active, complete, archived)--comment: Optional - Comment explaining the status change
Execution Instructions for Claude Code
When this command is run, Claude Code should:
- Validate that the PRD file exists
- Validate that the new status is one of the allowed values
- Read the current PRD metadata
- Check if the status transition is valid according to the lifecycle rules
- Update the PRD metadata:
- Change
statusfield to new status - Update
last_updatedto current date - If moving to APPROVED: prompt for
approved_byname and setapproved_date - If moving to ARCHIVED: add archive metadata section
- Change
- Add status change to a history section in the PRD (create if doesn't exist)
- Determine the new directory location based on status
- Move the file to the appropriate directory (using git mv if in git repo)
- Update any relative path references in the moved PRD
- Report the changes made
Status Transition Rules
Valid transitions:
- DRAFT → REVIEW, ARCHIVED
- REVIEW → APPROVED, DRAFT, ARCHIVED
- APPROVED → ACTIVE, REVIEW, ARCHIVED
- ACTIVE → COMPLETE, ARCHIVED
- COMPLETE → ARCHIVED
- ARCHIVED → (no transitions allowed)
Metadata Updates
Moving to APPROVED
status: APPROVED
approved_by: [Prompt for name]
approved_date: 2025-01-06
Moving to ARCHIVED
status: ARCHIVED
archive_date: 2025-01-06
archive_reason: [Use --comment or prompt]
final_task_completion: [Calculate if task file exists]
Status History Section
Add or update in PRD:
## Status History
- 2025-01-06: DRAFT → REVIEW (Ready for stakeholder feedback)
- 2025-01-07: REVIEW → APPROVED (Approved by Jane Smith)
- 2025-01-08: APPROVED → ACTIVE (Development started)
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.
- 1mo ago First seen · 133 lines · 11 tokens per session scan B a392b0560f68
prd-status is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 945 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.