How do I install the 0 Bash skill?

Run npx skillmds@latest add curvefit/0-bash 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 0 Bash safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 0 Bash?

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 0 Bash free to use?

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

Who published 0 Bash?

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

0 Bash by curvefit — Agent Skill

Name: 0 Bash
Author: curvefit

0 Bash

Bundle commands that Codex cannot execute because they require sudo, elevated permissions, or manual user execution into a single temporary Bash script. Use before a task to collect future blocked commands, or after Codex has already emitted manual command spam to convert it into one runnable script.

curvefit Updated Sep 22, 2026

File contents

Bundle Manual Commands

Keep working on every safe, executable part of the task. Collect only commands that the user must run, and hand back one temporary Bash script instead of a series of command snippets.

Build the script

Identify commands that cannot run in the current environment because they need elevation, unavailable access, or direct user execution.
Resolve exact targets and dependencies with read-only checks first. Do not use the script to bypass an approval that Codex can request normally.
Create one uniquely named file under ${TMPDIR:-/tmp}. Reuse that file for the rest of the task.
Start it with:
```
#!/usr/bin/env bash
set -euo pipefail
```
Append commands in dependency order. Add brief comments explaining purpose, required working directory, and any step that may prompt.
Quote paths and variables. Use sudo only on the individual commands that require it; do not require the whole script to run as root.
Make the script executable and syntax-check it with bash -n.

Continue adding newly discovered manual commands to the same script. If one must run before Codex can proceed, report that dependency promptly; otherwise defer the handoff until the task is complete.

Consolidate earlier commands

When manual commands have already been emitted, reconstruct them into one script in the order they must run. Remove duplicates and superseded alternatives. Preserve relevant flags and working-directory changes, and call out any ambiguity instead of guessing.

Safety

Never embed secrets, tokens, passwords, or private key material. Read them from environment variables or prompt at runtime without echoing.
Do not include destructive commands until their targets are exact and clearly authorized.
Do not widen the user's requested scope merely because execution is deferred to them.
Prefer idempotent checks when a command may be rerun.
Do not create an empty script when there are no manual commands.

Handoff

Return the script path, a one-line summary of what it does, and one command that runs it. Do not repeat every bundled command in the response. State whether running it is required to finish the current task and whether Codex needs its output afterward.

---name: 0-bashdescription: Bundle commands that Codex cannot execute because they require sudo, elevated permissions, or manual user execution into a single temporary Bash script. Use before a task to collect future blocked commands, or after Codex has already emitted manual command spam to convert it into one runnable script.---# Bundle Manual CommandsKeep working on every safe, executable part of the task. Collect only commands that the user must run, and hand back one temporary Bash script instead of a series of command snippets.## Build the script1. Identify commands that cannot run in the current environment because they need elevation, unavailable access, or direct user execution.2. Resolve exact targets and dependencies with read-only checks first. Do not use the script to bypass an approval that Codex can request normally.3. Create one uniquely named file under `${TMPDIR:-/tmp}`. Reuse that file for the rest of the task.4. Start it with: ```bash #!/usr/bin/env bash set -euo pipefail ```5. Append commands in dependency order. Add brief comments explaining purpose, required working directory, and any step that may prompt.6. Quote paths and variables. Use `sudo` only on the individual commands that require it; do not require the whole script to run as root.7. Make the script executable and syntax-check it with `bash -n`.Continue adding newly discovered manual commands to the same script. If one must run before Codex can proceed, report that dependency promptly; otherwise defer the handoff until the task is complete.## Consolidate earlier commandsWhen manual commands have already been emitted, reconstruct them into one script in the order they must run. Remove duplicates and superseded alternatives. Preserve relevant flags and working-directory changes, and call out any ambiguity instead of guessing.## Safety- Never embed secrets, tokens, passwords, or private key material. Read them from environment variables or prompt at runtime without echoing.- Do not include destructive commands until their targets are exact and clearly authorized.- Do not widen the user's requested scope merely because execution is deferred to them.- Prefer idempotent checks when a command may be rerun.- Do not create an empty script when there are no manual commands.## HandoffReturn the script path, a one-line summary of what it does, and one command that runs it. Do not repeat every bundled command in the response. State whether running it is required to finish the current task and whether Codex needs its output afterward.

Frequently asked questions