Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
dicklesworthstone avatar

Slb

  • 2 installs
  • 74 repo stars
  • Updated August 4, 2026
  • dicklesworthstone/simultaneous_launch_button

Enforces a two-person rule so a coding agent's destructive commands (rm -rf, force push, DROP TABLE) require peer review before executing.

About

Requires peer approval before running risky commands from AI agents, classifying commands into risk tiers with a notary daemon that verifies approvals. A developer uses it to gate destructive operations across coordinated agents.

  • Risk tiers from SAFE to CRITICAL with 0-2 required approvals
  • Five execution gates including hash tamper detection and atomic claim

Slb by the numbers

  • 2 all-time installs (skills.sh)
  • Ranked #1,786 of 2,203 Security skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/dicklesworthstone/simultaneous_launch_button --skill slb

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2
repo stars74
Last updatedAugust 4, 2026
Repositorydicklesworthstone/simultaneous_launch_button

What it does

Enforces a two-person rule so a coding agent's destructive commands (rm -rf, force push, DROP TABLE) require peer review before executing.

Files

SKILL.mdMarkdownGitHub ↗

<!-- TOC: Quick Start | THE EXACT PROMPT | Risk Tiers | Workflow | References -->

SLB — Simultaneous Launch Button

Core Capability: Two-person rule for running potentially destructive commands from AI coding agents. When an agent wants to run something risky, SLB requires peer review and explicit approval before execution.

Why This Exists

Coding agents can get tunnel vision, hallucinate, or misunderstand context. A second reviewer (ideally with a different model/tooling) catches mistakes before they become irreversible.

Critical: Commands run in YOUR shell environment, not on a server. The daemon is a NOTARY (verifies approvals), not an executor.

---

Quick Start

# Install
curl -fsSL https://raw.githubusercontent.com/Dicklesworthstone/slb/main/scripts/install.sh | bash

# Initialize project
cd /path/to/project
slb init

# Start session
slb session start --agent "GreenLake" --program "claude-code" --model "opus"

---

THE EXACT PROMPT — Basic Workflow

# 1. Run a dangerous command (blocks until approved)
slb run "rm -rf ./build" --reason "Clean build artifacts" --session-id <id>

# 2. Another agent reviews and approves
slb pending                    # See what's waiting
slb review <request-id>        # View full details
slb approve <request-id> --session-id <reviewer-id> --comment "Looks safe"

# 3. Original command executes automatically after approval

---

Risk Tiers

TierApprovalsAuto-approveExamples
CRITICAL2+Neverrm -rf /, DROP DATABASE, terraform destroy, git push --force
DANGEROUS1Neverrm -rf ./build, git reset --hard, kubectl delete, DROP TABLE
CAUTION0After 30srm file.txt, git branch -d, npm uninstall
SAFE0Immediatelyrm *.log, git stash, kubectl delete pod

---

Essential Commands

CategoryCommandDescription
Sessionslb session start --agent <name>Start agent session
Sessionslb session listShow active sessions
Requestslb run "<cmd>" --reason "..."Run dangerous command
Reviewslb pendingList pending requests
Reviewslb approve <id> --session-id <id>Approve request
Reviewslb reject <id> --reason "..."Reject request
Hookslb hook installInstall Claude Code hook
Patternslb patterns test "<cmd>"Check command tier

---

Claude Code Hook

# Install hook
slb hook install

# Hook actions:
# - allow: Command proceeds (SAFE tier)
# - ask: User prompted (CAUTION tier)
# - block: Blocked, must use `slb request` (DANGEROUS/CRITICAL tier)

---

Execution Verification (5 Gates)

GateCheck
1. StatusRequest must be APPROVED
2. ExpiryApproval TTL must not have elapsed
3. HashSHA-256 hash must match (tamper detection)
4. TierRisk tier must still match
5. First-ExecutorAtomic claim prevents race conditions

---

Emergency Override

For true emergencies, humans can bypass with extensive logging:

slb emergency-execute "rm -rf /tmp/broken" --reason "System emergency"

---

References

TopicReference
Full command referenceCOMMANDS.md
Pattern matching & tiersPATTERNS.md
ConfigurationCONFIG.md
Security designSECURITY.md

Related skills

Securityappsec

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.