safe-execution-edho-ferdian

Enforces mechanical pre-action gates around agent file edits and destructive commands.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/edhoferdian/EEF --skill safe-execution-edho-ferdian-edhoferdian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: safe-execution-edho-ferdian
Source: https://github.com/edhoferdian/EEF/tree/main/.agents/skills/safe-execution-edho-ferdian
Command: npx skills add https://github.com/edhoferdian/EEF --skill safe-execution-edho-ferdian-edhoferdian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous and parallel AI agents can edit files without investigating dependencies, run destructive commands like rm -rf or git push --force, write outside their assigned scope, and declare work done without recording it. Reasoning-based self-checks cannot catch these failures because self-evaluation shares the biases that produced the output. ## Core Features & Use Cases - Fact-forcing gate: Before the first edit to a file, the agent must produce concrete facts — importing files, affected public functions, actual data shapes, and the user's verbatim instruction. - Destructive-command guard: Every rm -rf, git reset --hard, DROP TABLE, kubectl delete, or --no-verify invocation requires an impact list and a rollback procedure before running. - Write-scope freeze and stop-gate: Freeze Mode locks writes to a named subtree for parallel agents, and a stop-gate blocks "done" until project-memory files were actually updated, verified via mtimes and counters. - Use Case: When dispatching several agents in parallel, each owning a slice of the repository, apply Gates 1-3 per agent so out-of-scope writes are refused at the moment they happen instead of discovered afterwards. ## Quick Start Ask the agent to apply the safe-execution gates before making any edits or running destructive commands in this session.

Frequently Asked Questions about safe-execution-edho-ferdian

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

FAQPage Schema
How do I stop an AI agent from editing files without checking dependencies first?

Apply a fact-forcing gate that blocks the first Edit or Write to a file until the agent lists every file that imports it, the affected public functions, and the actual data shapes involved. Once the facts are presented, further edits to that file proceed freely.

How to guard against destructive commands like rm -rf or git push --force?

Use a destructive-command guard that fires on every matching command, requiring a list of affected files and a one-line rollback procedure before execution. If a rollback cannot be written, the command should not run.

Can multiple AI agents write to the same repository in parallel safely?

Yes, by freezing each agent's write scope to its assigned subtree so out-of-scope writes are refused immediately. Only one writer should touch the filesystem per change; other agents produce diffs or patches for the writer to apply.

Why are self-evaluation checks unreliable for agent safety?

Asking a model whether it violated anything reliably returns no, because self-evaluation shares the biases that produced the output. Gates that demand produced artifacts or machine-verifiable facts change behavior instead of relying on introspection.

What are the limitations of mechanical execution gates?

They enforce the habit of investigation and record-keeping, not the quality of what is written. They complement rather than replace review and verification loops, and gates that cannot persist state should fail open with a warning.