v0.1.0 — first alpha

First alpha. A deterministic, offline CLI that finds broken agent
configuration — hooks whose scripts are gone, MCP servers that can never
start, credentials pasted into config, skills that disagree with their
lockfile.

What it does

bunx agentscan check                 # text report
bunx agentscan check --output prompt # paste-ready handoff for a fixing agent
bunx agentscan check --fail-on error # CI gate

23 checks, each one written against a published spec line recorded in
docs/spec/ with its source URL and the date it was read — not against
what happens to appear in real projects. That distinction is the whole
point of this release: an earlier build reported 37 findings across 17
projects of which 25 were false, because two checks were written
from observation. Both were deleted.

Score

score = max(0, 100 - 10 × errors - 3 × warnings)

Published deliberately. Measured across 21 projects it spans 40–100, and
it does not penalise a project for being large: an 85-skill project with
one warning scores 97, while a 54-skill one with six dead hooks scores
40. Coverage-ratio scoring was built, measured, and rejected for
inverting exactly that.

Requires Bun

Bun 1.1+. Not a Node build — import.meta.dir and Bun.which are used
directly. check never touches the network and never writes to the tree
being scanned; the only subprocess in the tool is the optional --copy
clipboard write.

Known limits

• Alpha. The finding-id format is a contract but the check set will move.
• Published as @chimix/agentscan — npm rejects the bare agentscan as
  too close to an unrelated agent-scan. The command stays agentscan.