stefankarpinski/karpinski-claude-plugins (process-probe)

Inspect a running process — its command line, environment variables, file descriptors, and network connections — through the credential-safe `process-probe` command (subcommands `env-keys`, `env-values`, `cmdline`, `info`, `fds`, `network`) that this plugin puts on your PATH. Never read /proc/PID/environ or /proc/PID/cmdline directly; the proc-probe-guard.sh PreToolUse hook blocks those reads across Bash, Read, Edit, Write, and NotebookEdit. The helpers redact values when either the variable name matches a sensitive-name keyword (password, secret, token, key, …) or the value matches a known credential shape (sk-…, ghp_…, AKIA…, JWT, PEM private key) or a length+entropy gate. A two-stage env workflow (list keys first, then explicitly request specific values) is the canonical entry point. Use this skill for any process probing — debugging a hang, diagnosing why something is stuck, checking what arguments or environment a daemon was started with, exploring file descriptors or network connections — even when the specific operation isn't itself credential-sensitive (the goal is one central, judgment-call-free place for all process probing).

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/stefankarpinski/karpinski-claude-plugins

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.

1 critical finding reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.