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 laurigates/claude-plugins --skill blueprint-adr-validategit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/blueprint-adr-validate)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/blueprint-adr-validate"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-adr-validate/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/laurigates/claude-plugins/blueprint-adr-validate"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-adr-validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.02607 |
| Opus 5.5 | $0.00016 | $0.01043 |
| Sonnet 5.5 | $0.00008 | $0.00521 |
| Haiku 4.5 | $0.00004 | $0.00261 |
Grade A, and why
blueprint-adr-validate 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 6d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/blueprint:adr-validate
Validate Architecture Decision Records for relationship consistency, reference integrity, and domain conflicts.
Usage: /blueprint:adr-validate [--report-only]
When to Use This Skill
| Use this skill when... | Use alternative when... |
|---|---|
| Maintaining ADR integrity before releases | Creating new ADRs (use /blueprint:derive-plans) |
| Auditing after refactoring or changes | Quick one-time documentation review |
| Regular documentation review process | General ADR reading |
Context
- ADR directory exists: !
find . -path '*/docs/adrs' -maxdepth 2 -type d - ADR count: !
find . -path '*/docs/adrs/*' -name "*.md" -type f - Domain-tagged ADRs: !
find . -path '*/docs/adrs/*' -maxdepth 3 -name '*.md' -exec grep -l "^domain:" {} + - Flag: !
echo "${1:---}"
Parameters
Parse $ARGUMENTS:
--report-only: Output validation report without prompting for fixes- Default: Interactive mode with remediation options
Execution
Execute complete ADR validation and remediation workflow:
Step 1: Discover all ADRs
- Check for ADR directory at
docs/adrs/ - If missing → Error: "No ADRs found in docs/adrs/"
- Parse all ADR files:
ls docs/adrs/*.md - Extract frontmatter for each ADR: number, id, created, modified, status, domain, supersedes, superseded-by, extends, relates-to
Step 2: Validate reference integrity
For each ADR, validate:
- supersedes references: Verify target exists, target status = "Superseded", target has reciprocal superseded-by
- extends references: Verify target exists, warn if target is "Superseded"
- related references: Verify all targets exist, warn if one-way links
- self-references: Flag if ADR references itself
- circular chains: Detect cycles in supersession graph
- Cross-workspace references (v3.3.0+, manifests with
workspaces.role): Recognise these reference forms in supersedes/extends/related fields:ADR-NNN— local to the current workspace (existing behaviour).<workspace-path>/ADR-NNN— points into a sibling/child workspace. Resolve by reading<workspace-path>/docs/adrs/from the monorepo root. Warn if the workspace is not listed in rootworkspaces.children./ADR-NNN— points at the monorepo root's ADR set. Resolve using the manifest'sworkspaces.root_relative_path(for child manifests) or the current directory (for root manifests). Unresolved cross-workspace refs are reported as warnings (not errors) so they do not block validation during migration.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago Changed · +1 lines 48662500509e
- 1mo ago First seen · 219 lines · 41 tokens per session scan A 00b309fa9949
blueprint-adr-validate is a skill published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 2,607 once invoked, about $0.0002 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
extract-ssot
Deduplicate repeated markdown (rule files, skill bodies, ADRs, docs) into one named source of truth and migrate every call site to cite it by exact heading. Use when the same prose, literal, or concept recurs across files: 'DRY this prose', 'extract a shared rule', 'single source of truth for X', a value-bump diff…
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…
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.
use-class-for-state
For complex state: encapsulate multiple interacting variables, stateful algorithms, backtracking search state.
display-grid-state
For 2D debugging: visualize grid/board state, show puzzle progress, make algorithm behavior visible.
renovate-triage
Use when triaging open Renovate PRs across your own repos into merge / close / defer. Activates on "renovate triage", "review dep PRs", "monthly deps", or on the 1st of a month if deps are grouped monthly.