safe-edit-simulator

safe-edit-simulator is a skill for Claude Code, Codex from pilinux/gorest. It costs 23 tokens per session (208 once invoked), scanned A, original, MIT.

A planning-only workflow for potentially disruptive code changes, such as authentication updates, security changes, database migrations, middleware changes, or deployment changes. It produces a simulated diff, risk checklist, rollback plan, and verification commands without editing files.

In plain words
What is it for?
Use it to prepare a dry run and assess risks before making changes to authentication, tokens, environment settings, databases, or deployments.
Why use it?
It lets you inspect likely effects and recovery steps before changing behavior that could affect access, configuration, or data. This reduces the chance of applying an unsafe change without a review plan.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to prepare a dry run and assess risks before making changes to authentication, tokens, environment settings, databases, or deployments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pilinux/gorest/safe-edit-simulator
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add pilinux/gorest --skill safe-edit-simulator
Clone the repo
git clone --depth 1 https://github.com/pilinux/gorest

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for safe-edit-simulator

README.md
[![agentmods](https://agentmods.dev/badge/skills/pilinux/gorest/safe-edit-simulator.svg)](https://agentmods.dev/skills/pilinux/gorest/safe-edit-simulator)
Your own site
<a href="https://agentmods.dev/skills/pilinux/gorest/safe-edit-simulator"><img src="https://agentmods.dev/badge/skills/pilinux/gorest/safe-edit-simulator.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 208 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00208
Opus 5 $0.00012 $0.00104
Sonnet 5 $0.00005 $0.00042
Haiku 4.5 $0.00002 $0.00021

Measured 9d ago against content hash 56c9446e0e29, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

safe-edit-simulator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/safe-edit-simulator/SKILL.md · 37 lines

What it actually says

Safe Edit Simulator

When to Use

  • Before applying changes that affect auth, security, DB migrations, middleware, or deployment behavior.

Responsibilities

  • Produce a readable dry-run diff and summarize changed hunks.
  • Enumerate risks and mitigation steps.
  • Provide a concise rollback plan and verification commands.

Rules

  • Do not apply changes; only simulate and document.
  • Call out impacts on authentication, token validation, env/config, and data integrity.

Output

  • Dry-run diff: summary of files and hunks.
  • Risk checklist: 3-8 items with severity.
  • Rollback: single-line plan.
  • Verify: 1-3 commands.
  • fix-suggester, patch-applier, qa-orchestrator
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 37 lines · 23 tokens per session scan A 56c9446e0e29

Subscribe to this mod's changes

safe-edit-simulator is a skill published in the GitHub repository pilinux/gorest (504 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 208 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.