blueprint-docs-list

blueprint-docs-list is a skill for Claude Code from laurigates/claude-plugins. It costs 40 tokens per session (1,164 once invoked), scanned A, original, MIT.

A listing tool for Blueprint documents, including PRDs, ADRs, and PRPs, with their metadata. ADRs record important architecture choices; PRDs describe product requirements; PRPs guide implementation.

In plain words
What is it for?
Use it to list documents, inspect their frontmatter, audit statuses, or generate an index of Blueprint documentation.
Why use it?
It gives a single overview of project documents and their statuses instead of requiring people to inspect folders one by one. This makes documentation audits and indexes easier.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Part of the blueprint-plugin plugin — 35 skills shipped together

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 skills/laurigates/claude-plugins/blueprint-docs-list
Any agent
npx skills add laurigates/claude-plugins --skill blueprint-docs-list
Clone the repo
git clone --depth 1 https://github.com/laurigates/claude-plugins

Made for: Claude Code.

Or install blueprint-plugin, the plugin that ships this one along with the rest of its 35 skills.

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 blueprint-docs-list

README.md
[![agentmods](https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-docs-list.svg)](https://agentmods.dev/skills/laurigates/claude-plugins/blueprint-docs-list)
Your own site
<a href="https://agentmods.dev/skills/laurigates/claude-plugins/blueprint-docs-list"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-docs-list.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,164 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.1 $0.00040 $0.01164
Opus 5 $0.00020 $0.00582
Sonnet 5 $0.00008 $0.00233
Haiku 4.5 $0.00004 $0.00116

Measured yesterday against content hash 8c20c973334a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

blueprint-docs-list 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 yesterday.

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.

blueprint-plugin/skills/blueprint-docs-list/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

List blueprint documents programmatically from the filesystem. Extracts metadata from YAML frontmatter and markdown headers.

When to Use This Skill

Use this skill when... Use blueprint-adr-list instead when...
You want a combined index of ADRs, PRDs, and PRPs (or summary across all) You only need an ADR-specific index table
You want to audit document statuses across all blueprint types You need ADR-specific fields like domain or status filtering
You want a quick overview using all to see counts of every doc type You're generating an ADR index for a README

Use Case: Audit document status, generate index tables, or get a quick overview of all project documentation.

Parameters

Arg Description
adrs List Architecture Decision Records
prds List Product Requirements Documents
prps List Product Requirement Prompts
all Summary of all document types

Execution

If arg is adrs

Run /blueprint:adr-list — it handles ADR-specific extraction with both header-section and frontmatter support.

If arg is prds

printf "| PRD | Title | Status | Date |\n|-----|-------|--------|------|\n" && \
for f in docs/prds/*.md; do
  [ -f "$f" ] || continue
  fname=$(basename "$f")
  [ "$fname" = "README.md" ] && continue
  doc_title=$(head -50 "$f" | grep -m1 "^title:" | sed 's/^title:[[:space:]]*//' || true)
  doc_status=$(head -50 "$f" | grep -m1 "^status:" | sed 's/^status:[[:space:]]*//' || true)
  doc_date=$(head -50 "$f" | grep -m1 "^date:\|^created:" | sed 's/^[^:]*:[[:space:]]*//' || true)
  # Fallback: extract title from H1
  if [ -z "$doc_title" ]; then
    doc_title=$(head -20 "$f" | grep -m1 "^# " | sed 's/^# //')
  fi
  printf "| [%s](%s) | %s | %s | %s |\n" \
    "${fname%.md}" "$f" "${doc_title:-(untitled)}" "${doc_status:--}" "${doc_date:--}"
done

If arg is prps

printf "| PRP | Title | Status | Confidence |\n|-----|-------|--------|------------|\n" && \
for f in docs/prps/*.md; do
  [ -f "$f" ] || continue
  fname=$(basename "$f")
  [ "$fname" = "README.md" ] && continue
  doc_title=$(head -50 "$f" | grep -m1 "^title:" | sed 's/^title:[[:space:]]*//' || true)
  doc_status=$(head -50 "$f" | grep -m1 "^status:" | sed 's/^status:[[:space:]]*//' || true)
  doc_confidence=$(head -50 "$f" | grep -m1 "^confidence:" | sed 's/^confidence:[[:space:]]*//' || true)
  if [ -z "$doc_title" ]; then
    doc_title=$(head -20 "$f" | grep -m1 "^# " | sed 's/^# //')
  fi
  printf "| [%s](%s) | %s | %s | %s |\n" \
    "${fname%.md}" "$f" "${doc_title:-(untitled)}" "${doc_status:--}" "${doc_confidence:--}"
done

Read the full file on GitHub · 104 lines

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. yesterday First seen · 104 lines · 40 tokens per session scan A 8c20c973334a

Subscribe to this mod's changes

blueprint-docs-list is a skill published in the GitHub repository laurigates/claude-plugins (58 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,164 once invoked, about $0.0002 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-09-03.