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 rp1-run/rp1 --skill blueprint-archivegit clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/rp1-run/rp1/blueprint-archive)<a href="https://agentmods.dev/skills/rp1-run/rp1/blueprint-archive"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/blueprint-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/rp1-run/rp1/blueprint-archive"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/blueprint-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.00021 | $0.00708 |
| Opus 5.5 | $0.00008 | $0.00283 |
| Sonnet 5.5 | $0.00004 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
blueprint-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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Archive
Archives completed PRD docs from active -> archives dir with associated features.
Usage
/rp1-dev:blueprint-archive <prd-name>
Behavior
- Moves
.rp1/work/prds/<PRD_NAME>.md->.rp1/work/archives/prds/<PRD_NAME>/prd.md - Archives associated completed features to
.rp1/work/archives/features/ - Generates
closure_summary.mdwith archive metadata - Checks KB staleness and suggests
/knowledge-buildif needed - Creates archive directories if missing
Execution
Step 1: Scan PRD
{% dispatch_agent "rp1-dev:prd-archiver" %} MODE: scan PRD_NAME: {PRD_NAME} KB_ROOT: {kbRoot} WORK_ROOT: {workRoot} {% enddispatch_agent %}
Step 2: Handle Scan Response
Parse JSON response from agent.
Error Response (type: "error"):
{"type":"error","message":"...","available_prds":["prd1","prd2"]}
Output error message with available PRDs list, then STOP.
Needs Confirmation (type: "needs_confirmation"):
{
"type": "needs_confirmation",
"prd_name": "...",
"prd_title": "...",
"associated_features": [...],
"message": "..."
}
Continue to Step 3.
Step 3: Confirm Closure Status
{% ask_user "Archive PRD '{PRD_NAME}' ({prd_title})? {message}", options: "Yes - Objectives fully met", "Partial - Some objectives met", "No - Cancel" %}
Handle response:
- "Yes": Go to Step 4 with
CLOSURE_STATUS=complete - "Partial": Go to Step 4a
- "No": Output
Archive aborted by user.+ STOP
Step 4a: Document Gaps (Partial Only)
{% ask_user "Document the gaps or unmet objectives:" %}
Capture response as GAPS.
Step 4: Execute Archive
{% dispatch_agent "rp1-dev:prd-archiver" %} MODE: archive PRD_NAME: {PRD_NAME} CLOSURE_STATUS: {complete|partial} GAPS: {user-provided gaps or empty} KB_ROOT: {kbRoot} WORK_ROOT: {workRoot} {% enddispatch_agent %}
Step 5: Report
Display agent success output directly. Include:
- PRD name and archive location
- Features archived vs skipped
- KB staleness suggestion if applicable
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 · 110 lines · 21 tokens per session scan A d740eb5e362a
blueprint-archive is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 16d ago), licensed Apache-2.0. It adds 21 tokens to every session and 708 once invoked, about $0.0001 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-07.
Other skills, from other repositories
openspec-bulk-archive-change
Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
product-management
Expertise in product management lifecycle, from ideation to launch. Covers requirements gathering, user story creation, prioritization, and product strategy. Use this skill for product planning, writing PRDs, defining MVPs, or competitive analysis.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach. Also use when the user says "openspec new change" or "opsx new".
openspec-archive-change
Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".
prd-to-plan
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".