nygenome

Probe Run — Development skill for Claude Code

Development community

/probe-run — Step 2 of probe tracking: forensic Lancet2 invocation.

How to install Probe Run

Installs to ~/.claude/commands/nygenome-lancet2-probe-run.md

Terminal

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/nygenome/Lancet2/HEAD/.claude/commands/probe-run.md -o ~/.claude/commands/nygenome-lancet2-probe-run.md

Restart Claude Code, or start a new session, for it to be picked up.

What Probe Run does

/probe-run — Step 2 of probe tracking: forensic Lancet2 invocation

Re-run Lancet2 with `--probe-variants` and `--probe-results` to collect forensic data on every missed truth variant. This is step 2 in the probe tracking workflow; step 1 (`/probe-concordance`) produced the missed variants list this step needs as input.

The probe system records raw facts per `(probe_id, window, comp_id, k)` attempt — no attribution logic, just a TSV of survival counts and structural flags. Step 3 (`/probe-ana

Alternatives in Development

Bypass 403 — Probe a 403/401 endpoint with the most-paid bypass tricks (header injection, path encoding, method swap, WAF f 4.5k ★
Agent Instructions — This project uses bd (beads) for issue tracking 1.6k ★
Claude Balancer — A load balancer proxy for multiple Claude OAuth accounts with automatic failover, request tracking, and web da 910 ★