scan

A command that scans documentation files for broken links and examples that are no longer current.

In plain words
What is it for?
It helps check Markdown files under the docs folder, verify internal and external links, and report each problem with its file and line.
Why use it?
It finds documentation problems before readers or developers encounter dead links or outdated instructions.

Command

Part of the doc-checker plugin — 1 command 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 commands/stbenjam/skillsaw/scan
Clone the repo
git clone --depth 1 https://github.com/stbenjam/skillsaw

Or install doc-checker, the plugin that ships this one along with the rest of its 1 command.

Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 63 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 $0.00005 $0.00063
Opus 5 $0.00003 $0.00032
Sonnet 5 $0.00001 $0.00013
Haiku 4.5 $0.00001 $0.00006

Measured 3d ago against content hash 0c4375697e57, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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.

tests/fixtures/autofix/fixable-accuracy-marketplace-root/pkgs/doc-checker/commands/scan.md · 12 lines

What it actually says

Scan docs

Scan the documentation tree for broken links and out-of-date examples.

  1. Crawl every markdown file under docs/.
  2. Check internal links resolve and external links return 200.
  3. Report each broken link with its file and line.
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. 3d ago First seen · 12 lines · 5 tokens per session scan A 0c4375697e57

Subscribe to this mod's changes

scan is a command published in the GitHub repository stbenjam/skillsaw (59 stars, last pushed 3d ago), licensed Apache-2.0. It adds 5 tokens to every session and 63 once invoked, about $0.0000 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-08-30.