bas3line

Airsec — Security skill for Claude Code

Security community

Find Security Issues in your code by using coding CLIs like Claude, Codex & CommandCode.

How to install Airsec

This entry records only its repository, not the path inside it, so there is no exact command to give. Open bas3line/Airsec and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Airsec does

Find Security Issues in your code by using coding CLIs like Claude, Codex & CommandCode.

Alternatives in Security

Anthropic Cybersecurity Skills — 734+ structured cybersecurity skills for AI agents · MITRE ATT&CK mapped · agentskills.io open standard · Work 3.8k ★
OpenTag — Open-source, channel-native agent gateway for Slack 499 ★
Security Check — Scan project for security issues — exposed secrets, missing .gitignore entries, unsafe patterns 335 ★

README

airsec

**State-of-the-art security review, driven by the coding CLI you already have.**

Claude Code · Codex · OpenCode · Command Code

[![ci](https://github.com/bas3line/Airsec/actions/workflows/ci.yml/badge.svg)](https://github.com/bas3line/Airsec/actions/workflows/ci.yml) [![license: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) [![node](https://img.shields.io/badge/node-%E2%89%A520-brightgreen.svg)](#requirements)

No new API key. No cloud upload. No third-party scanner. airsec drives the agent already installed on your machine through a structured, multi-pass security audit, then turns the result into a report you can act on.

Quick start

npx airsec@latest init

That is the whole thing. `init` walks you through it: pick the folder, pick your coding CLI, pick the model, choose review-or-fix, and it runs.

Other ways to install

npm  install -g airsec      # global
pnpm add    -g airsec
bun  add    -g airsec
yarn global add airsec

airsec init                 # then run it anywhere

No `curl | sh` installer, deliberately: a tool that audits your code for supply-chain risk should not ask you to pipe a URL into a shell.

Getting ETARGET · No matching version found?

Your npm is pointed at a mirror that has not synced the release yet. Check with `npm config get registry` — if it is anything other than `https://registry.npmjs.org`, either wait for the mirror to catch up or bypass it:

npx --registry=https://registry.npmjs.org airsec@latest init   # one-off
npm config set registry https://registry.npmjs.org             # permanently

Requirements

Node ≥ 20 (the published bundle has zero runtime dependencies)
At least one supported coding CLI on your PATH — check with npx airsec harness