Samples — Process Docs & Runbooks for Operating VulnHunter
This folder holds sample operational documentation for running the VulnHunter harness and skills: a standard operating procedure (SOP), a process-optimization analysis, and step-by-step runbooks. They were authored with the doc-coauthoring and operations (process-doc, runbook, process-optimization) workflows.
These are reference samples for onboarding. Commands and config keys are exact (verified against the source), but roles, contacts, thresholds, and metric targets are placeholders — adapt them to your own organization before operational use. All commands assume you are authorized to scan the target repositories.
Contents
samples/
├── process/
│ ├── harness-usage-process.md ← SOP: end-to-end Find→Fix→Verify (purpose, scope, RACI, flow, steps, exceptions, metrics)
│ └── process-optimization.md ← before/after analysis: automate the loop, cut handoffs & waiting
└── runbooks/
├── runbook-01-install-setup.md ← install skills + harness + agent; set the model
├── runbook-02-batch-scan.md ← scan many repos with the harness (REPO_LIST → collect)
├── runbook-03-benchmark.md ← measure detection accuracy vs a known-vuln corpus
├── runbook-04-scan-fix-verify-loop.md ← one repo, all three skills interactively
└── runbook-05-headless-agent.md ← unattended scan in CI + GitHub issues (vulnhunter-agent)
Where to start
| You want to… | Read |
|---|---|
| Understand the whole operating model | process/harness-usage-process.md |
| Get a workstation ready | runbooks/runbook-01-install-setup.md |
| Scan one repo and fix + verify a finding | runbooks/runbook-04-scan-fix-verify-loop.md |
| Sweep a whole portfolio | runbooks/runbook-02-batch-scan.md |
| Prove accuracy before adopting | runbooks/runbook-03-benchmark.md |
| Automate scanning in CI | runbooks/runbook-05-headless-agent.md |
| Make the process faster/leaner | process/process-optimization.md |
Safety reminders (baked into every doc)
- The scanner never edits code. Only
/vulnhunter-fixwrites — on a git branch/worktree, operator-gated./vulnhunt-fix-verifyis strictly read-only (no Bash, no network). - All parts send code to a model provider. Scan only repositories you are authorized to analyze; note the cyber-safeguard / Cyber Verification Program requirement on Anthropic first-party platforms.
- Prefer read-only scans; reserve bash-enabled (runs exploit tests) for trusted code.
Related
- Architecture & module docs:
../docs/· interactive../architecture.html - Knowledge base (Obsidian):
../CapOne vulnhunter/