Borrowing it
Nothing to install: this file belongs to r3bl-org/r3bl-open-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/r3bl-org/r3bl-open-core/main/.agents/skills/safe-renaming/SKILL.mdgit clone --depth 1 https://github.com/r3bl-org/r3bl-open-coreWrote 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/skills/r3bl-org/r3bl-open-core/safe-renaming)<a href="https://agentmods.dev/skills/r3bl-org/r3bl-open-core/safe-renaming"><img src="https://agentmods.dev/badge/skills/r3bl-org/r3bl-open-core/safe-renaming/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/r3bl-org/r3bl-open-core/safe-renaming"><img src="https://agentmods.dev/badge/skills/r3bl-org/r3bl-open-core/safe-renaming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 21 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 21 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00032 | $0.00701 |
| Opus 5.5 | $0.00013 | $0.00280 |
| Sonnet 5.5 | $0.00006 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade C, and why
safe-renaming scanned grade C with 1 finding 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 11d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/Downloads/rename-staging How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use This Skill
Activate this skill whenever the user asks for rename requests (e.g., "Rename X to Y across the codebase", "tree-wide rename", "safely rename ..."), or any renaming of variables, fields, functions, parameters, or types across files in the codebase.
Mandate: No Scripts of Any Kind
Scripts of ANY kind (shell scripts like perl, sed, awk, python, bash, fish, or custom/disposable Rust scripts compiled via rustc) are STRICTLY PROHIBITED for performing code refactoring or modifications. All changes must be performed file-by-file using native file-editing tools (replace_file_content / multi_replace_file_content) combined with AST-level semantic tools (rust-analyzer).
Workflow: Safe Staged Refactoring Protocol
To ensure safety during multi-file refactoring, follow this protocol:
Step 1: Optional BTRFS Staging Copy
For large changes, use cp --reflink=auto to create a lightweight, near-instant BTRFS CoW snapshot copy of the workspace in ~/Downloads/rename-staging/.
# Ensure any previous staging directory is clean
rm -rf ~/Downloads/rename-staging
# Create BTRFS reflink clone
cp --reflink=auto -r ~/github/roc ~/Downloads/rename-staging
Step 2: Systematic File-by-File Native Edits
Perform the refactoring file-by-file using native file editing tools (replace_file_content / multi_replace_file_content) and semantic AST tools:
- Search and inspect target occurrences using AST references or grep.
- Carefully apply edits line-by-line or chunk-by-chunk to preserve surrounding rustdoc, formatting, and comments.
- Beware of local variable shadowing (e.g.
let vp_width = ...shadowingvp_width(...)).
Step 3: Incremental Validation
After modifying a batch of 3-5 files, run fast type/lint validation directly and delegate long-running test/doc checks to a background subagent (invoke_subagent with TypeName: "self", Model: "inherit"):
./check.fish --check
./check.fish --clippy
./check.fish --test
./check.fish --quick-doc
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.
- 11d ago Changed c95caec81a63
- 2mo ago First seen · 53 lines · 32 tokens per session scan C f8b8dd71bf01
safe-renaming is a skill published in the GitHub repository r3bl-org/r3bl-open-core (486 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 701 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gmail
Search, read, draft, and send Gmail when the user asks to work with their inbox or email.
google-calendar
Read schedules, check availability, and create or update Google Calendar events when the user asks to work with their calendar.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
unifly
Inspect and manage UniFi Network infrastructure with the unifly CLI: devices, clients, VLANs, WiFi, firewall, VPN, switch ports, site settings, and cloud fleets. Use for UniFi network configuration, monitoring, and troubleshooting, not UniFi Protect camera or recording management.
unifly
Inspect and manage UniFi Network infrastructure with the unifly CLI: devices, clients, VLANs, WiFi, firewall, VPN, switch ports, site settings, and cloud fleets. Use for UniFi network configuration, monitoring, and troubleshooting, not UniFi Protect camera or recording management.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.