J-0-S-E

Linux Airlock — Git skill for Claude Code

Git community

Stops sketchy AUR packages, themes and github repos at the door, before they get anywhere near your linux Computer.

How to install Linux Airlock

This entry records only its repository, not the path inside it, so there is no exact command to give. Open J-0-S-E/linux-airlock and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Linux Airlock does

Stops sketchy AUR packages, themes and github repos at the door, before they get anywhere near your linux Computer. A claude code skill + a tiny scanner script, because clamav wasn't gonna save me anyway

Alternatives in Git

40+ Claude Code Tips — Tips for getting the most out of Claude Code, including a custom status line script, cutting the system prompt 5.8k ★
Claude Code Statusline — by rz1989s - Enhanced 4-line statusline for Claude Code with themes, cost tracking, and MCP server monitoring 398 ★
The Agentic Startup — by Rudolf Schmidt - Yet Another Claude Orchestrator - a collection of agents, commands, etc., for shipping pro 226 ★

README

linux-airlock

Stuff has to go through the airlock before it gets on your computer. That's it, that's the idea!

Why tho

So I was setting up security on my computer (CachyOS, Arch-based) and asked Claude why ClamAV is so slow. Turns out it doesn't even matter how slow it is, because it's mostly looking for Windows viruses. That's not what's gonna get you on Linux!

What actually gets you is **stuff you install yourself**. An AUR package, a cool Hyprland theme, some dotfiles with an `install.sh`, a random GitHub repo. That code runs as you, so it doesn't even need root to encrypt your home folder or grab your SSH keys and browser sessions.

And no, this isn't hypothetical:

July 2025: Three -bin browser packages on the AUR shipped with the Chaos RAT [1] [2]
Spring 2026: The "Atomic Arch" campaign took over orphaned AUR packages and had the PKGBUILD pull in a malicious npm package that stole cookies, SSH keys, tokens, all of it [3] [1]
August 2026: Another wave hit 89+ AUR packages (openconnect-sso and friends), and Arch had to lock pushes to the AUR completely [4] [5]
March 2024: A global theme in the KDE Store ran rm -rf and wiped a user's files. It was a bug, not malware, but it proved the point: KDE themes and widgets can run any code they want [6] [7]
2026: Thousands of fake GitHub repos with READMEs written to trick AI agents (yes, like Claude!?) into running the install script without looking, aka "AgentBaiting" [8]

The numbers jump down to the [Sources](#sources) at the bottom, where you can see the full link before you click anything. Some of them are news sites and security blogs, not Arch's own announcements, and they don't all agree on the exact numbers.

I also wanted something like this for Claude Code and co