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.
git clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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.
[](https://agentmods.dev/commands/yeaight7/agent-powerups/safe-rename)<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>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.
| Model | Per session | Once 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 |
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.
What it actually says
Safe Rename Command
CRITICAL BEHAVIORAL RULES
- 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.
- Search First: Do not guess where the name is used. Use a broad grep search to find all occurrences of
<old_name>. - Atomic Commits: If the rename spans multiple subsystems, plan to apply the rename incrementally rather than in one massive replace if possible.
- Verify: After applying the rename, run the test suite again. If it fails, revert the change immediately and report the error.
Execution Steps
- Run the test suite to confirm a green state.
- Search the codebase for exact matches of the old name.
- Apply the rename. Check for casing variations (e.g.,
OldName,oldName,old_name) if appropriate for the language context. - If renaming a file, ensure all import paths referencing that file are also updated.
- Run the test suite again.
- Provide a summary of the files modified and the final test output.
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.
- 7d ago First seen · 22 lines · 23 tokens per session scan A 51bf770325aa
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.
Other commands, from other repositories
audit-accessibility
Audit web page or component for WCAG accessibility compliance.
t800-update
A command for updating the T-800 agent system from its GitHub repository. GitHub is a service for storing and versioning code.
validate-pipeline
Validate data pipeline configuration and data quality rules.
t800-bootstrap
A first-run setup command for the T-800 plugin, intended for installation or a new user.
advisor
Get a second opinion from Codex (GPT-5) on your current plan, diff, or a specific question.
aidd-churn
Rank files by hotspot score to identify prime candidates for refactoring before PR review.