How do I install the Keel Secure skill?

Run npx skillmds@latest add sayeediftekhar/keel-secure in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Keel Secure safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Keel Secure?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Keel Secure free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Keel Secure?

sayeediftekhar (@sayeediftekhar) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Keel Secure by sayeediftekhar — Agent Skill

Name: Keel Secure
Author: sayeediftekhar

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.

File contents

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.

---name: keel-securedescription: 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.---# 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 beforeit's called done.## Deference — keel-v2 is the arbiterThis lane *implements* the keel-v2 security posture; it never relaxes it. Achange touching danger surfaces 3/4/9 (PII, auth, secrets) is HEAVY bydefinition (keel-v2 LAWS). VibeSec's findings feed the keel-v2 /reviewtripwire "if any danger surface is live, both named enforcement layers arepresent."## 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)1. `keel-dev` (or any lane) produces a change touching a trust boundary.2. Route here → run `VibeSec-Skill` over the diff.3. 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).4. 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 installedDo **not** silently skip the security pass. Say VibeSec isn't installed, runthe keel-v2 tripwire manually (trace each trust boundary, name both enforcementlayers), and flag that an automated scan was unavailable. Install:`./install.sh secure`.Sources: BehiSecc/VibeSec-Skill (vibesec.sh). Upstream unmodified.

Frequently asked questions