hardstop

Block dangerous shell commands and credential file reads before execution.

31|2|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/frmoretto/hardstop --skill hardstop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hardstop
Source: https://github.com/frmoretto/hardstop/tree/main/.claude/skills/hardstop
Command: npx skills add https://github.com/frmoretto/hardstop --skill hardstop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents AI-driven or user-initiated shell commands and file reads from causing harm by enforcing a pre-execution safety protocol and guarding against credential exposure.

Core Features & Use Cases

  • Pre-execution protocol: Instant block checks, risk assessment, signal of confidence, and explicit confirmation for risky actions before execution.
  • Credential read protection: Blocks reading of sensitive files like ~/.ssh, ~/.aws, ~/.env, and other credentials sources.
  • LLM-awareness for non-hook environments: Provides safety guidance when no deterministic hooks are available.
  • Transparent rationale and logs: Shares why a command is blocked or allowed to help user understanding.

Quick Start

Instruct the skill to review commands before execution, for example: "Please evaluate the following shell command: rm -rf ~/" and respond with whether to block or allow.

Frequently Asked Questions about hardstop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent AI from running dangerous shell commands in my terminal?

Pre-execution safety protocols block dangerous shell commands by applying instant risk assessments and requiring explicit user confirmation before execution, covering Unix-like and Windows environments.

How do I stop AI prompts from reading sensitive credential files like SSH keys or AWS configs?

Credential read protection blocks AI from reading sensitive files such as ~/.ssh, ~/.aws, and ~/.env. It warns on risky file reads and prevents access to credential sources to guard against accidental exposure.

Does this shell command blocking approach work on both Unix and Windows systems?

Yes, the shell command blocking protocol applies across both Unix-like and Windows environments. It covers commands, file reads, and credential access with layered risk assessment regardless of the operating system.

What is a pre-execution protocol for AI safety and how does it work?

A pre-execution protocol for AI safety works by performing instant block checks, evaluating risk levels, signaling confidence, and prompting for explicit user confirmation before allowing any potentially dangerous shell command to run.

Can I use AI shell safety mechanisms without deterministic execution hooks?

Yes, LLM-aware safety guidance provides protection when no deterministic hooks are available in the environment. It evaluates commands and shares transparent rationale on why a command is blocked or allowed.