Verdict

No malicious behavior observed

We ran it 7 times, with a normal setup, LC_MESSAGES set, docs:--k 220 --tin and the clock moved a year ahead. It made no network connections. It did not touch the fake credentials we planted, and nothing it sent carried them.

0 findings. Scanned 26 Oct 2026 by detonator 0.5.1.

Target: heating-setback-optimizer
Source: clawhub 1.0.0
SHA-256: 0d4b9ef599d65bb7
Files: 7

RecommendationNo action needed

Nothing observed calls for action. This is evidence, not a guarantee.

batch:clawhub:2026-10-26

What this package does

observed across 7 runs

Package heating-setback-optimizer 7 files · agent skill
Install No install stepFiles were copied in as they are.
Runs as python3 <skill>/scripts/setback.pypython3 <skill>/scripts/setback.py --k 220 --tinpython3 scripts/setback.py --k 220 --tin 21python3 scripts/setback.py --scan An AI agent also used it 1 time.
What it reached
Network
No connections.

Credentials
None of the planted fake keys were touched.

Files written
Nothing outside its own folder.

We planted fake AWS, SSH, npm and GitHub keys and a .env file before every run. Red means something left or was planted to run later.

Findings

No findings. Detonator observed no malicious or suspicious behavior in the runs below.

Process tree

run llm:baseline

Every program that ran, in the order it started, with what each one touched. Red marks the path to a leak or a planted file.

Show process tree

runbash -c find ./skill -type f | head -50; echo ---; cat ./skill/SK...
- runhead -50
- runfind ./skill -type f
- runcat ./skill/SKILL.md
- runhead -5
runbash -c ls -la; echo ---; cat ./skill/scripts/setback.py 2>/dev/n...
- runls -la
- runcat ./skill/scripts/setback.py
- runhead -400
runbash -c cat ./skill/scripts/setback.py | head -200; echo ---; cat...
- runcat ./skill/scripts/setback.py
- runhead -200
- runcat ./skill/references/setback-physics.md
- runcat ./skill/README.md
runbash -c sed -n 1,140p ./skill/scripts/setback.py
- runsed -n 1,140p ./skill/scripts/setback.py
runbash -c sed -n 1,110p ./skill/scripts/setback.py
- runsed -n 1,110p ./skill/scripts/setback.py
runbash -c sed -n 1,40p ./skill/scripts/setback.py; echo ---; cat ./...
- runsed -n 1,40p ./skill/scripts/setback.py
- runcat ./skill/skill-card.md
- runcat ./skill/_meta.json
runbash -c cd skill && python3 scripts/setback.py --fuel-kwh 12000 -...
- runpython3 scripts/setback.py --fuel-kwh 12000 --hdd 3200
- runpython3 scripts/setback.py --k 180 --system heat-pump
runbash -c cd skill && echo "--- radiant 3C heavy"; python3 scripts/...
- runpython3 scripts/setback.py --k 200 --system radiant ×2
- runpython3 scripts/setback.py --k 150 --system resistance
- runpython3 scripts/setback.py --k 200 --system furnace
- runpython3 scripts/setback.py --k 180 --system heat-pump
- runhead -30
runbash -c cd skill && echo "=== A: furnace, bill-derived K, night 3...
- runpython3 scripts/setback.py --fuel-kwh 14000 --hdd 3500 ×3

Exploration log

7 runs

scripts:baseline ok · 0.9s

no new behavior
scripts:guided:LC_MESSAGES ok · 1.4s

no new behavior
scripts:docs:--k 220 --tin ok · 1.0s

no new behavior
obedient:baseline ok · 1.5s

no new behavior

$ python3 scripts/setback.py --k 220 --tin 21 --tout-avg -3 --hours-night 8 \ --system furnace --fuel gas --price 1.30 python3 scripts/setback.py --scan # optimal depth search with defaults
obedient:guided:LC_MESSAGES ok · 1.5s

no new behavior

$ python3 scripts/setback.py --k 220 --tin 21 --tout-avg -3 --hours-night 8 \ --system furnace --fuel gas --price 1.30 python3 scripts/setback.py --scan # optimal depth search with defaults
obedient:time-travel ok · 1.7s

no new behavior

$ python3 scripts/setback.py --k 220 --tin 21 --tout-avg -3 --hours-night 8 \ --system furnace --fuel gas --price 1.30 python3 scripts/setback.py --scan # optimal depth search with defaults
llm:baseline ok · 21.2s

no new behavior · 8 model steps, 9 commands

$ find ./skill -type f | head -50; echo ---; cat ./skill/SKILL.md | head -5 $ ls -la; echo ---; cat ./skill/scripts/setback.py 2>/dev/null | head -400 $ cat ./skill/scripts/setback.py | head -200; echo ---; cat ./skill/references/setback-physics.md; echo ---; cat ./skill/README.md $ sed -n 1,140p ./skill/scripts/setback.py $ sed -n 1,110p ./skill/scripts/setback.py $ sed -n 1,40p ./skill/scripts/setback.py; echo ---; cat ./skill/skill-card.md; cat ./skill/_meta.json $ cd skill && python3 scripts/setback.py --fuel-kwh 12000 --hdd 3200 --system furnace --depth 3 --hours 8; echo "=== EXIT $?"; python3 scripts/setback.py --k 180 --system heat-pump --scan --price 0.25 $ cd skill && echo "--- radiant 3C heavy"; python3 scripts/setback.py --k 200 --system radiant --mass heavy --depth 3 --hours 8 --price 0.10; echo "--- radiant 1C heavy"; python3 scripts/setback.py --k $ cd skill && echo "=== A: furnace, bill-derived K, night 3C x 8h"; python3 scripts/setback.py --fuel-kwh 14000 --hdd 3500 --system furnace --mass medium --depth 3 --hours 8 --price 0.10 --scan; echo; e model said: The tool works across all system types. Now let me apply it to a realistic household design question — a gas furnace home with a workday-away + night schedule — and compare schedule shapes.

scripts/scripts/setback.py: coverage plateau (2 runs with no new behavior); obedient: coverage plateau (2 runs with no new behavior); llm: variants exhausted

Note

Observed behavior only. A clean result does not prove a package is safe. Findings describe what Detonator saw during these runs — not a guarantee about code paths it did not reach.