debug-pro@2.1.5
VERIFIED· install onlyPublisher claims: "A language-agnostic 7-step debugging protocol (reproduce -) locate the layer -) minimize -) hypothesize -) verify -) fix -) regress) with a zero-dependency, offline toolchain that turns 'I reproduced it' into checkable evidence: triage extracts exception type, last stack frame, exit code, HTTP status and timestamps from raw logs; envsnap builds a paste-ready environment block with every key containing KEY/TOKEN/SECRET/PASS/CRED/AUTH/COOKIE redacted; reprocheck grades the five minimum elements of a reproduction report and names the missing ones. Ships a 10-case golden set with a re-executable runner, a real error-log demo, a layered symptom lookup, a 5-item pre-delivery self-check and degradation rules. Faithful by design: no unobserved cause is ever invented, and any claim lacking reproducible evidence is explicitly marked unconfirmed. Generic methodology tool - not a medical device, no clinical or efficacy claims." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 3 of 3 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What changed since 2.1.4
vet-skills diff debug-pro 2.1.4 2.1.5In the sandbox, this version reached for nothing 2.1.4 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 92/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
item["git_rev"] = subprocess.run(["git", "rev-parse", "--short", "HEAD"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.No other findings across 1,151 lines in 19 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.