scan

scan is a skill for Claude Code from dgalarza/claude-code-workflows. It costs 17 tokens per session (1,482 once invoked), scanned A, original, MIT.

A read-only scan that checks whether project documentation still matches the codebase. Documentation drift happens when files such as README or architecture notes describe code that has since changed.

In plain words
What is it for?
Use it to scan configured documentation, compare its file and code references with the repository, and report places where the written information no longer reflects the code.
Why use it?
It finds outdated references without modifying the project. This helps teams locate inaccurate documentation before it misleads developers.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

Part of the doc-sentinel plugin — 3 skills, 1 agent, 2 hooks shipped together

Good fit Use it to scan configured documentation, compare its file and code references with the repository, and report places where the written information no longer reflects the code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dgalarza/claude-code-workflows/scan
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.

Any agent
npx skills add dgalarza/claude-code-workflows --skill scan
Clone the repo
git clone --depth 1 https://github.com/dgalarza/claude-code-workflows

Made for: Claude Code.

Or install doc-sentinel, the plugin that ships this one along with the rest of its 3 skills, 1 agent, 2 hooks.

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 scan

README.md
[![agentmods](https://agentmods.dev/badge/skills/dgalarza/claude-code-workflows/scan/github.svg)](https://agentmods.dev/skills/dgalarza/claude-code-workflows/scan)
Your own site
<a href="https://agentmods.dev/skills/dgalarza/claude-code-workflows/scan"><img src="https://agentmods.dev/badge/skills/dgalarza/claude-code-workflows/scan/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.

agentmods 80×15 button for scan

Your own site · 80×15
<a href="https://agentmods.dev/skills/dgalarza/claude-code-workflows/scan"><img src="https://agentmods.dev/badge/skills/dgalarza/claude-code-workflows/scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,482 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00017 $0.01482
Opus 5.5 $0.00007 $0.00593
Sonnet 5.5 $0.00003 $0.00296
Haiku 4.5 $0.00002 $0.00148

Measured 1mo ago against content hash 4471a02d2b6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

scan 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.

plugins/doc-sentinel/skills/scan/SKILL.md · 187 lines

How it starts

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

doc-sentinel:scan

Deep scan that cross-references all documentation against the current state of the codebase. Unlike the hook (which checks only files changed in a commit), this scans everything.

This skill is read-only — it reports drift but does not modify files.

Phase 1: Load Configuration

cat .doc-sentinel.json 2>/dev/null || echo "No config — using defaults"

Defaults if no config:

  • docs_root: docs
  • watch_files: AGENTS.md, ARCHITECTURE.md, README.md, CLAUDE.md
  • ignore_sources: *.test.*, *.spec.*, __tests__/**

Phase 2: Discover Documentation

Collect all doc files:

# docs/ directory
find docs/ -name '*.md' -type f 2>/dev/null | sort

# Top-level docs
for f in AGENTS.md ARCHITECTURE.md CLAUDE.md README.md CHANGELOG.md; do
  [ -f "$f" ] && echo "$f"
done

Plus any watch_files from config.

Phase 3: Extract References

For each doc file, extract references to source code:

3a: File Path References

Search for paths that look like source file references:

# Extract paths from backticks, links, and code blocks
grep -oE '`[a-zA-Z0-9_./-]+\.(ts|js|py|rb|go|rs|java|tsx|jsx)`' "$doc_file"
grep -oE '\b(src|lib|app|packages)/[a-zA-Z0-9_./-]+' "$doc_file"

3b: Command References

Extract shell commands documented in the file:

# Find code blocks with shell commands
grep -E '^\$|^pnpm |^npm |^yarn |^cargo |^go |^bundle |^python |^make ' "$doc_file"

3c: Port and URL References

grep -oE '(localhost|127\.0\.0\.1):[0-9]+' "$doc_file"
grep -oE ':[0-9]{4,5}\b' "$doc_file"

3d: Environment Variable References

grep -oE '\$\{?[A-Z_][A-Z0-9_]*\}?' "$doc_file"
grep -oE '`[A-Z_][A-Z0-9_]*`' "$doc_file"

Phase 4: Validate References

For each extracted reference, check if it still holds:

4a: File Paths — Do They Exist?

# For each extracted path
[ -f "$path" ] && echo "OK: $path" || echo "DRIFT: $path — file not found"

4b: Directory References — Do They Exist?

Read the full file on GitHub · 187 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. 1mo ago First seen · 187 lines · 17 tokens per session scan A 4471a02d2b6c

Subscribe to this mod's changes

scan is a skill published in the GitHub repository dgalarza/claude-code-workflows (62 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 1,482 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-08-30.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens