consequence-simulation
Skill10 starsChanged todayMITView on GitHub
Simulate action consequences, blast radius, and reversibility tiers before human-in-the-loop approvals
- Deletes or force-pushes
In this repository44 other files it gives its agents.
- llms-full.txtllms.txt
- llms.txtllms.txt
- ai-prompt-engineering-safety-reviewSkill
- ast-codemapSkill
- ast-grepSkill
- autoharnessSkill
- autonomous-backlog-driverSkill
- claude-kimi-mcp-normalizationSkill
- cli-self-updaterSkill
- code-frugalitySkill
- codemode-gatewaySkill
- codemode-typesSkill
- context-pruningSkill
- github-update-checkerSkill
- google-agents-cli-evalSkill
- google-agents-cli-scaffoldSkill
- history-searchSkill
- hook-gatingSkill
- hybrid-semantic-searchSkill
- kimi-code-agent-integrationSkill
- kimi-mcp-configurationSkill
- leann-vectorSkill
- log-summarizerSkill
- markdown-vagueSkill
- memory-reconciliationSkill
- mode-classificationSkill
- multiagent-orchestrationSkill
- output-compressionSkill
- prompt-injectionSkill
- python-anti-patternsSkill
- regression-sentinelSkill
- restart-trackingSkill
- rollback-guardSkill
- rust-call-graphSkill
- secrets-managementSkill
- security-best-practicesSkill
- session-compactorSkill
- sqlite-memorySkill
- swarm-barrierSkill
- swarm-dagSkill
- autoharnessSkill
- code-reliability-checksSkill
- skill-threat-rulesSkill
- autoharnessSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use before requesting user approval or executing high-impact actions (file deletions, gateway reconfigurations, migrations, architectural …
- Very specific: line 21
Use AST Call Graph (codemap.analyze_impact) to locate direct callers, callees, and impacted test suites.
- Very specific: line 33
Run pytest tests/test_consequence_simulation.py to verify risk categorization and blast radius calculations.
- Very specific: line 34
Run autoharness permissions simulate <action> and check terminal output.
- Very specific: line 35
Verify Gateway MCP tool harness_simulate_action.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
consequence-simulation
When to use
Use before requesting user approval or executing high-impact actions (file deletions, gateway reconfigurations, migrations, architectural boundary edits). Grounded in Hugging Face arXiv:2610.40753, this skill replaces blind confirmation prompts with structured consequence simulations.
Steps
- Action Classification:
Identify action type:
file_delete,file_modify,gateway_reconfig,command_exec,schema_change. - Reversibility Tier Assignment:
IRREVERSIBLE: Deleting untracked files, dropping tables,git clean -fdx, overwriting data without backup.HIGH_RISK: Reconfiguring MCP gateway (gateway.json), modifying core state or security integrity keys, editing files with wide blast radius (>5 dependents).REVERSIBLE: Modifying git-tracked files, creating new tests or branches, editing isolated utilities.READ_ONLY: Static inspection, queries, AST codemap, test runs without side-effects.
- Blast Radius Analysis:
- Compute affected files and directory hierarchy.
- Use AST Call Graph (
codemap.analyze_impact) to locate direct callers, callees, and impacted test suites. - Detect if boundary rules or architectural layers are breached.
- Generate Consequence Manifest:
- Format a clear Markdown/JSON summary outlining:
- Action & Target
- Reversibility Tier & Risk Score (0-100)
- Impacted Files & Symbols
- Rollback Plan / Recovery Path
- Format a clear Markdown/JSON summary outlining:
- Present to User / Agent:
- Deliver the simulation report alongside the approval dialog.
How to verify
- Run
pytest tests/test_consequence_simulation.pyto verify risk categorization and blast radius calculations. - Run
autoharness permissions simulate <action>and check terminal output. - Verify Gateway MCP tool
harness_simulate_action.
Facts found here
- Hugging Face arXiv:2610.40753 demonstrates that providing consequence simulation reduces catastrophic agent errors by over 60% compared to binary "Allow/Deny" prompts.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

