Scan
- Updated June 25, 2026
- twofoldtech-dakota/sleuth
scan is a Claude Code plugin marketplace that publishes sleuth so developers can install harness discovery tooling and generate evidence-linked System Dossiers from any project.
About
scan is the Claude Code marketplace entry for twofoldtech-dakota/sleuth, packaging the sleuth plugin that performs read-only archaeology on Claude Code harnesses. Developers reach for it when they need an installable marketplace path to ranked System Dossiers about load-bearing, dangerous, and dead harness elements. Add twofoldtech-dakota/sleuth, install sleuth@scan, then run /sleuth:sleuth against any target harness directory.
- Marketplace name scan; plugin command /sleuth:sleuth
- Same harvest-plus-synthesis pipeline as the sleuth skill repo
- Writes sleuth-dossier markdown with path:line citations
- Eval fixture proves harvester discrimination; synthesis is model-run
Scan by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add twofoldtech-dakota/sleuthAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| Last updated | June 25, 2026 |
|---|---|
| Repository | twofoldtech-dakota/sleuth ↗ |
How do you install and run repeatable Claude Code harness archaeology without copying ad hoc audit scripts into every repository?
Install the sleuth marketplace plugin to run read-only Claude Code harness archaeology and emit evidence-linked System Dossiers.
Who is it for?
Developers who prefer marketplace install of sleuth and want monthly dossier diffs on complex .claude configurations.
Skip if: Engineers seeking write-time code generation or teams with no Claude Code plugins, skills, or hooks to inspect.
What you get
An installed sleuth plugin run that outputs sleuth-dossier markdown with ranked, cited harness findings in the working directory.
Plugins in this marketplace
1 plugin - install individually after you add the marketplace.
Recommended Marketplaces
FAQ
How is Scan related to sleuth?
README says the marketplace repo contains the sleuth plugin; marketplace name is Scan and users install sleuth@Scan.
What command runs the audit?
After install, run /sleuth:sleuth with a target harness path; output is sleuth-dossier markdown in the working directory.
Is the audit destructive?
README emphasizes read-only analysis against the target with inference backed by path:line citations.