safe-rename

safe-rename is a command for Claude Code from yeaight7/agent-powerups. It costs 23 tokens per session (294 once invoked), scanned A, original, Apache-2.0.

A repository-wide rename command for variables, functions, classes, and files. It searches for every use, updates related imports, and checks tests before and after the change.

In plain words
What is it for?
Renaming code symbols or files across a project, including updating file import paths and checking the modified files and test results.
Why use it?
It reduces the risk of missing references or leaving the code broken after a rename. If tests fail after the change, it reverts the rename and reports the error.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the codebase-maintenance plugin — 8 skills, 4 commands, 3 agents shipped together

Good fit Renaming code symbols or files across a project, including updating file import paths and checking the modified files and test results.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/yeaight7/agent-powerups/safe-rename
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.

Clone the repo
git clone --depth 1 https://github.com/yeaight7/agent-powerups

Made for: Claude Code.

Or install codebase-maintenance, the plugin that ships this one along with the rest of its 8 skills, 4 commands, 3 agents.

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-rename

README.md
[![agentmods](https://agentmods.dev/badge/commands/yeaight7/agent-powerups/safe-rename.svg)](https://agentmods.dev/commands/yeaight7/agent-powerups/safe-rename)
Your own site
<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/safe-rename"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/safe-rename.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 294 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.
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.00294
Opus 5 $0.00012 $0.00147
Sonnet 5 $0.00005 $0.00059
Haiku 4.5 $0.00002 $0.00029

Measured 7d ago against content hash 51bf770325aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

safe-rename 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 7d 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.

plugins/codebase-maintenance/commands/safe-rename.md · 22 lines

What it actually says

Safe Rename Command

CRITICAL BEHAVIORAL RULES

  1. Test Verification: Before you change any code, you MUST run the test suite to ensure it is currently green. If tests are failing before you start, stop and report the failure.
  2. Search First: Do not guess where the name is used. Use a broad grep search to find all occurrences of <old_name>.
  3. Atomic Commits: If the rename spans multiple subsystems, plan to apply the rename incrementally rather than in one massive replace if possible.
  4. Verify: After applying the rename, run the test suite again. If it fails, revert the change immediately and report the error.

Execution Steps

  1. Run the test suite to confirm a green state.
  2. Search the codebase for exact matches of the old name.
  3. Apply the rename. Check for casing variations (e.g., OldName, oldName, old_name) if appropriate for the language context.
  4. If renaming a file, ensure all import paths referencing that file are also updated.
  5. Run the test suite again.
  6. Provide a summary of the files modified and the final test output.
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. 7d ago First seen · 22 lines · 23 tokens per session scan A 51bf770325aa

Subscribe to this mod's changes

safe-rename is a command published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 294 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-31.