Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jpoutrin/product-forgenpx agentmods add skills/jpoutrin/product-forge/prd-archiveWrote 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-archive)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/prd-archive"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/prd-archive/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-archive"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/prd-archive.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.00010 | $0.01256 |
| Opus 5.5 | $0.00004 | $0.00502 |
| Sonnet 5.5 | $0.00002 | $0.00251 |
| Haiku 4.5 | $0.00001 | $0.00126 |
Grade A, and why
prd-archive 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prd-archive
Category: Product & Strategy
Usage
prd-archive <prd-file> [--reason <reason>] [--force]
Arguments
<prd-file>: Required - Path to the PRD file to archive--reason: Optional - Reason for archiving (default: "Implementation complete" or "Project cancelled")--force: Optional - Archive even if status is not COMPLETE or ARCHIVED
Execution Instructions for Claude Code
When this command is run, Claude Code should:
- Read the PRD file and validate it exists
- Check current status:
- If COMPLETE: proceed with archiving
- If ARCHIVED: warn that it's already archived
- If other status and no --force: ask for confirmation
- If PRD has a linked task file, calculate final completion percentage
- Add archive metadata to the PRD:
- archive_date
- archive_reason
- final_task_completion (if applicable)
- implementation_duration (if dates available)
- Determine archive location:
- Extract year from last_updated or use current year
- Create path:
product-docs/prds/archive/YYYY/ - For cancelled PRDs:
product-docs/prds/archive/YYYY/cancelled/
- Move the PRD file to archive location (use git mv if in git repo)
- Update status to ARCHIVED
- Optionally archive the linked task file to the same location
- Create an archive summary file if this is the first archive of the month
Archive Metadata
Add to PRD header before moving:
status: ARCHIVED
archive_date: 2025-01-06
archive_reason: Implementation complete - v1.0 released
final_task_completion: 100%
implementation_duration: 15 days
original_location: product-docs/prds/active/feature-prds/
Archive Directory Structure
product-docs/prds/archive/
├── 2025/
│ ├── Q1/
│ │ ├── completed/
│ │ │ ├── user-auth-frd.md
│ │ │ └── user-auth-frd-tasks.md
│ │ ├── cancelled/
│ │ │ └── experimental-feature-frd.md
│ │ └── 2025-Q1-archive-summary.md
│ └── Q2/
└── 2024/
Output Format
📦 Archiving PRD: user-authentication-frd.md
Current Status: COMPLETE
Task Completion: 100% (20/20 tasks)
✅ Adding archive metadata:
- archive_date: 2025-01-06
- archive_reason: Implementation complete - v1.0 released
- final_task_completion: 100%
- implementation_duration: 15 days
📁 Moving to archive:
From: product-docs/prds/active/feature-prds/user-authentication-frd.md
To: product-docs/prds/archive/2025/Q1/completed/user-authentication-frd.md
📄 Also archiving linked task file:
To: product-docs/prds/archive/2025/Q1/completed/user-authentication-frd-tasks.md
✅ Archive complete!
📊 Archive Summary:
- Implementation started: 2024-12-22
- Implementation completed: 2025-01-06
- Total duration: 15 days
- Final status: Successfully delivered
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 · 168 lines · 10 tokens per session scan A f92d9cc714d6
prd-archive is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 1,256 once invoked, about $0.0000 per session on Opus 5.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-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.