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 document-detectiongit 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/document-detection)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/document-detection"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/document-detection/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/document-detection"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/document-detection.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.00037 | $0.02395 |
| Opus 5.5 | $0.00015 | $0.00958 |
| Sonnet 5.5 | $0.00007 | $0.00479 |
| Haiku 4.5 | $0.00004 | $0.00239 |
Grade A, and why
document-detection 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 18d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Detection
Proactively identify when conversations should become structured documents (PRDs, ADRs, or PRPs) and guide users through the documentation workflow.
When to Use This Skill
| Use this skill when... | Use blueprint-derive-plans instead when... |
|---|---|
| Mid-conversation cues suggest a PRD/ADR/PRP should be captured | You're explicitly deriving plans (PRDs/ADRs/PRPs) from existing README/docs and git history |
| The user says "I want to build...", "users should be able to..." | Use blueprint-derive-plans instead when the cue is a tech-choice decision worth an ADR |
| The user compares trade-offs ("should we use X or Y?") | Use document-linking instead to wire IDs across already-created docs |
| Implementation scope is being discussed and warrants a PRP | Use blueprint-prp-create instead when you've already decided to author a PRP |
When This Skill Activates
This skill is loaded when conversation context suggests documentation opportunities:
- Feature requirements being discussed
- Architecture decisions being made
- Implementation planning in progress
- Technology trade-offs being evaluated
Prerequisites
Document detection requires:
- Blueprint initialized in project (
docs/blueprint/manifest.jsonexists) has_document_detection: truein manifest structuredocs/directory structure created
Check prerequisites before prompting:
# Verify blueprint is initialized with document detection enabled
jq -r '.structure.has_document_detection // false' docs/blueprint/manifest.json 2>/dev/null
Detection Patterns
PRD Indicators (Product Requirements)
Primary triggers (confidence +0.5 each):
- Feature descriptions: "I want to build...", "The system should...", "We need a feature that..."
- User stories: "As a [user], I want...", "Users should be able to..."
- Requirements enumeration: Lists of features or capabilities
- Problem/solution framing: "The problem is... the solution is..."
Confidence boosters (+0.1-0.2 each):
- Multiple features mentioned (+0.2)
- User personas identified (+0.1)
- Success criteria discussed (+0.1)
- Priority levels mentioned (P0, P1, must-have, nice-to-have) (+0.1)
- Timeline or milestones mentioned (+0.1)
What ships with it
3 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.
- 18d ago Changed · -70 lines 976c81856405
- 1mo ago First seen · 345 lines · 37 tokens per session scan A a0e3652591b7
document-detection is a skill published in the GitHub repository laurigates/claude-plugins (59 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 2,395 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-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…
motion-design
Craft rules for anything that moves on a timeline, in video or UI: animate this, motion graphics, title card, intro or outro, transition, explainer that feels like slides, easing, timing, how long to hold text. Gives numeric defaults, an accessibility gate and the tells of generated-looking motion.
performance
Profiling-driven performance optimization: caching, query tuning, N+1 fixes, memory, and load testing. Use to diagnose a bottleneck or set performance budgets.
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.
oslog
Read, stream, and analyze Apple unified logs (OSLog) for iOS/macOS apps. Auto-detects subsystem from Logger usage or bundle identifier. Supports live log show, real-time streaming, and .logarchive analysis with full predicate reference. Use when the user asks to check app logs, stream console output, debug with OSLog…