Keel secure

Skill sayeediftekhar/Keel/skills/keel-secure

Security lane router and gate. Runs VibeSec over security-relevant code to catch vulnerabilities before they ship, and wires that check into keel-v2's security tripwire. Defers to keel-v2. Use when a change touches auth, input handling, secrets, uploads, queries, or any trust boundary — or when asked to review code for vulnerabilities.From its SKILL.md

Install

npx -y skills add sayeediftekhar/Keel --skill keel-secure

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 449 tokens by cl100k_base, as published. Nobody here has run it

Keel Secure — security lane router & gate

Index + gate. Unlike the other lanes this one is also a checkpoint: any security-relevant change routed from keel-dev passes through here before it's called done.

Deference — keel-v2 is the arbiter

This lane implements the keel-v2 security posture; it never relaxes it. A change touching danger surfaces 3/4/9 (PII, auth, secrets) is HEAVY by definition (keel-v2 LAWS). VibeSec's findings feed the keel-v2 /review tripwire "if any danger surface is live, both named enforcement layers are present."

Dispatch table

When the task is…	Dispatch to	Type	Source
Write/review code for vulnerabilities (injection, authz, secrets, SSRF, XSS)	`VibeSec-Skill`	skill	BehiSecc/VibeSec-Skill

Gate rule (how it plugs into keel-v2)

keel-dev (or any lane) produces a change touching a trust boundary.
Route here → run VibeSec-Skill over the diff.
Map each finding to a keel-v2 invariant (server-enforces, identity-from- session, exact-money, immutable-records). A finding with only one enforcement layer present = PARTIAL, not done (keel-v2 LAWS).
Unresolved high-severity finding = block the commit gate. Upgrading rigor is yours to enforce; downgrading is only the human's explicit call.

If the target isn't installed

Do not silently skip the security pass. Say VibeSec isn't installed, run the keel-v2 tripwire manually (trace each trust boundary, name both enforcement layers), and flag that an automated scan was unavailable. Install: ./install.sh secure.

Sources: BehiSecc/VibeSec-Skill (vibesec.sh). Upstream unmodified.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most security skills give in 449 tokens

Counted across 648 of the 828 authors here whose files we hold, read 2026-08-07

Parameterize all database queriesin 68 of 648, across 51 files
Hash passwords using bcrypt, scrypt, or argon2in 49 of 648, across 36 files
Apply rate limiting to authentication endpointsin 48 of 648, across 24 files
Configure security headersin 35 of 648, across 19 files
Validate all inputsin 32 of 648, across 24 files
Validate all external input at the system boundaryin 29 of 648, across 19 files
Run containers as a non-root userin 28 of 648, across 15 files
Use httponly secure samesite cookies for sessionsin 26 of 648, across 15 files
Run dependency audits before every releasein 21 of 648, across 10 files
Encode output to prevent cross-site scriptingin 21 of 648, across 11 files
Copy dependencies before source codein 20 of 648, across 9 files
Store secrets in environment variablesin 20 of 648, across 18 files

Said here and by no other author read

route trust boundary changes through this gate
run VibeSec over the diff
map each finding to an invariant
require both enforcement layers on live danger surfaces
treat single layer findings as partial
block commit gate on unresolved high severity findings

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.