document-linking

document-linking is a skill for Claude Code from laurigates/claude-plugins. It costs 47 tokens per session (3,201 once invoked), scanned A, original, MIT.

A system for assigning consistent IDs and connecting requirements documents, architecture decisions, implementation plans, work orders, and GitHub issues.

In plain words
What is it for?
Use it to assign missing IDs, create two-way links, validate references, and find orphaned documents or issues.
Why use it?
It makes relationships between project documents easier to follow and helps find broken links or documents that are not connected to anything.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the TodoWrite tool; positional $N argument.

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/document-linking
Any agent
npx skills add laurigates/claude-plugins --skill document-linking
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 document-linking

README.md
[![agentmods](https://agentmods.dev/badge/skills/laurigates/claude-plugins/document-linking.svg)](https://agentmods.dev/skills/laurigates/claude-plugins/document-linking)
Your own site
<a href="https://agentmods.dev/skills/laurigates/claude-plugins/document-linking"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/document-linking.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,201 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.00047 $0.03201
Opus 5 $0.00023 $0.01600
Sonnet 5 $0.00009 $0.00640
Haiku 4.5 $0.00005 $0.00320

Measured 2d ago against content hash cf43f2f0aa51, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

document-linking 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 2d 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.

blueprint-plugin/skills/document-linking/SKILL.md · 437 lines

How it starts

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

Document Linking

Provides a unified ID system connecting PRDs, ADRs, PRPs, work-orders, GitHub issues, commits, and PRs. IDs are project-scoped, auto-generated on first access, and maintained bidirectionally.

When to Use This Skill

Use this skill when... Use blueprint-sync-ids instead when...
You need bidirectional links between PRD/ADR/PRP/issue at runtime You're doing a one-shot bulk ID assignment for docs missing IDs
You're auto-assigning an ID on first document access You want a --dry-run preview of bulk ID changes
You want to validate broken cross-document references Use blueprint-adr-validate instead for ADR-only relationship checks
You need to find orphan docs/issues across the project Use document-detection instead when capturing a brand-new doc

ID Format

Document Type Format Example Notes
PRD PRD-NNN PRD-001 3-digit, zero-padded
ADR ADR-NNNN ADR-0003 4-digit (matches existing convention)
PRP PRP-NNN PRP-007 3-digit, zero-padded
Work-Order WO-NNN WO-042 3-digit, matches work-order number

Frontmatter Schema

All blueprint documents should include these fields:

---
id: PRD-001                    # Unique identifier (auto-generated if missing)
relates-to:                    # Cross-document references (optional)
  - ADR-0003
  - PRP-002
github-issues:                 # Linked GitHub issues (optional)
  - 42
  - 87
implements:                    # For PRPs: source PRD (optional)
  - PRD-001
# ... existing fields (created, modified, status, etc.)
---

ID Registry (manifest.json)

IDs are tracked in docs/blueprint/manifest.json:

{
  "id_registry": {
    "last_prd": 3,
    "last_prp": 7,
    "documents": {
      "PRD-001": {
        "path": "docs/prds/user-authentication.md",
        "github_issues": [42, 87],
        "title": "User Authentication"
      },
      "ADR-0003": {
        "path": "docs/adrs/0003-database-choice.md",
        "github_issues": [],
        "title": "Database Choice"
      },
      "PRP-002": {
        "path": "docs/prps/oauth-integration.md",
        "github_issues": [45],
        "implements": ["PRD-001"],
        "title": "OAuth Integration"
      }
    },
    "github_issues": {
      "42": ["PRD-001", "PRP-002"],
      "45": ["PRP-002"],
      "87": ["PRD-001"]
    }
  }
}

Read the full file on GitHub · 437 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. 2d ago First seen · 437 lines · 47 tokens per session scan A cf43f2f0aa51

Subscribe to this mod's changes

document-linking is a skill published in the GitHub repository laurigates/claude-plugins (58 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 3,201 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.

Related

Other skills, from other repositories

extract-ssot

Deduplicate repeated markdown content, rule files, skill bodies, ADRs, docs, into a single named source of truth and migrate every call site to cite it by exact heading. Use when the same prose, literal, or concept appears (or is reworded) across files: 'DRY this prose', 'extract a shared rule', 'single source of…

melodic-software/claude-code-plugins · 130 tokens

feature-branch-pr-writing

Use this skill when the user asks to write, draft, create, or improve a PR description for a Shopware core repository PR — AND that PR targets a non-trunk feature branch (not trunk itself). Trigger phrases like "write a PR description", "draft the PR", "what should I put in the PR body". The skill detects the target…

shopwareLabs/ai-coding-tools · 152 tokens

ci-log-interpretation

Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…

shopwareLabs/ai-coding-tools · 154 tokens

repo-activity

Scan all git repositories under /repos and report recent activity — last commit age, branch, uncommitted changes — in age-bucketed tables. Use when the user asks for a repo activity overview, "what have I been working on", portfolio status, or which repos are active/dormant.

laurigates/dotfiles · 65 tokens

a0-create-plugin

Create, extend, or modify Agent Zero plugins. Follows strict full-stack conventions (usr/plugins, plugin.yaml, Store Gating, AgentContext, plugin settings). Use for UI hooks, API handlers, lifecycle extensions, or plugin settings UI.

Gen-Verse/PAST-Bench · 54 tokens

a0-contribute-plugin

Guide for publishing an Agent Zero plugin to the community Plugin Index (a0-plugins repo). Covers GitHub repo setup, index.yaml creation, CI validation rules, and PR submission. Use when the user wants to share, publish, submit, or contribute a plugin to the Plugin Hub so other Agent Zero users can find and install it.

Gen-Verse/PAST-Bench · 74 tokens