What the source did
- He's a chemical plant operator, not an IT professional. He applies continuous improvement to his homelab.
- His agents run under strict rules: a restore point before every change, a guard that blocks destructive commands, nothing irreversible without his explicit approval, and every change goes through a pull request he reviews.
- With Opus 5.5 he asked for a full audit of servers, websites, scripts, backups and the automation that keeps things updated. It found things to improve, but nothing fishy.
- With Fable 5.2 on trial, he ran the same audit and asked it to challenge everything built so far.
- While cleaning an old 2 TB download folder, it built a read-only inventory and matched every video against his library by exact file size. It flagged three fakes: two "movies" that were Windows .exe files and one "TV episode" that was a 1.1 GB Windows .lnk shortcut.
- It never opened them. It explained they're harmless on a Linux NAS but dangerous with one double-click from a Windows PC on the network share, and then it waited for his OK.
- In comments, he says he uses Claude Code desktop over SSH, runs gitleaks, and that the only client playing from that share is an Android TV box.
- Most likely, his Arr suite grabbed fake releases. The media manager refused to import them, so they sat in the download folder.
“Everything goes through pull requests, with a restore point before any change”— u/Rizel68 (r/ClaudeAI), Reddit
Summary written by Agent Cookbook from the original post. See the original for the full context. How we source recipes
Our notes
- What it takes
- Claude Code on your desktop, connected over SSH to the server; a restore point before every change; a guard that blocks destructive commands; gitleaks for secret scanning; and pull requests you review. He didn't publish his guard or restore-point setup, so the rules brief is ours.
- Where it breaks
- Opening a suspicious file: a Windows program or shortcut is harmless on a Linux NAS but can run on one double-click from a Windows PC on the share. Rejected downloads can sit in the folder when the media manager won't import them. His model comparison is his trial experience; we didn't reproduce it.
- Human checkpoint
- Nothing irreversible runs without your explicit OK. Every change is a pull request you review, and deleting the flagged files is your call.
- Tools involved
- Claude Code, on your desktop, connected over SSH to the server, A restore point before every change (a backup or snapshot you can roll back to), A guard that blocks destructive commands, gitleaks, to keep secrets out of what the agent commits, Pull requests, so you review every change before it lands, You, approving anything irreversible
✓ Verified Source link checked and still live. Notes by Thomas, editor. How we verify
Copy the prompt
Ours Our version, based on u/Rizel68's post. He didn't publish his prompt, repo or rules file, so this uses only the rules and steps he described. Fill in the [BRACKETS].
Approval rule
Set it up
- Set the rules first: a restore point before any change, a guard on destructive commands, explicit approval for anything irreversible, and changes only as pull requests you review.
- Connect the agent to the server, read-only first. He used Claude Code desktop over SSH.
- Run a full audit of servers, websites, scripts, backups and the automation that keeps things updated.
- Build a read-only inventory of the download folder, and match each video to your library by exact file size.
- Check each unmatched file's real type from its file header. Don't open or run it.
- Scan for secrets with gitleaks, and wait for your OK before any change.
Common failures
- Opening a suspicious file to see what it is. On a Linux NAS a Windows program or shortcut is harmless, but one double-click from a Windows PC on the share can run it.
- Leaving rejected downloads in the folder. His media manager refused to import the fakes, so they sat there until the audit.
- Stopping at one audit pass. His Opus 5.5 pass found nothing fishy; the fakes came up in the later run on the trial model.
Variations
- Check which clients can open each network share. In his setup, the only client playing from the share was an Android TV box.
Related setups: An AWS audit that starts read-only → · Slack Approve/Cancel gate for Claude Code bots → · Get notified when your coding agent needs you →
Get the 10 best agent setups. Free.
Plus new recipes every week. One email, no spam.
Unsubscribe anytime. Privacy