Safe Bash

Name: Safe Bash
Author: apsethicsbowl20026-collab

BSecurity

Run shell via `bash_exec`. Server blocks destructive commands — don't try to bypass.

2 stars
0 votes
0 copies
1 view
Added October 17, 2026

ai-agentsrustshellbashgit

Security analysis

B85/100

highPerforms destructive filesystem operations

Pro shows the line behind each finding and how to fix it

Scanned October 17, 2026

npx -y skills add apsethicsbowl20026-collab/open-computer-skills --skill safe-bash --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Safe Bash?

Add the live security badge to your README. It updates with every re-scan.

[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/apsethicsbowl20026-collab-safe-bash/badge)](https://www.skillsdirectory.com/skills/apsethicsbowl20026-collab-safe-bash)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

# safe-bash

Run shell via `bash_exec`. Server blocks destructive commands — don't try to bypass.

## Blocked (non-exhaustive)

`rm -rf /`, `rm -rf ~`, `mkfs`, `dd of=/dev/`, `shutdown`, `reboot`, `diskpart`, registry deletes, `net user /add`, disabling Defender/Firewall.

## Rules

- Prefer read-only first: `ls`, `pwd`, `git status`, `echo`.
- Chain with `&&` only after first command succeeds.
- Paste full stdout/stderr + exit code in your report.
- Never run curl-piped-to-shell from untrusted URLs.