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.
npx skills add ZaxbyHub/opencode-swarm --skill safe-renamegit clone --depth 1 https://github.com/ZaxbyHub/opencode-swarmWrote 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/zaxbyhub/opencode-swarm/safe-rename)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/safe-rename"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/safe-rename/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/zaxbyhub/opencode-swarm/safe-rename"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/safe-rename.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.02266 |
| Opus 5.5 | $0.00019 | $0.00906 |
| Sonnet 5.5 | $0.00010 | $0.00453 |
| Haiku 4.5 | $0.00005 | $0.00227 |
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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Safe Rename Skill
Guides a systematic, tool-augmented workflow for renaming exported symbols across a codebase without silently breaking consumers, tests, or downstream builds.
When to Use
- Renaming an exported function, class, interface, type alias, constant, or enum across the codebase.
- Renaming a file that is imported by other modules (requires updating all import paths).
- Any rename where the old symbol name appears in more than one file.
Do NOT use for:
- Local-only renames (a variable scoped to a single function body) — use your editor's rename refactoring directly.
- Renaming a symbol that has zero consumers — just edit the definition.
Required Tools
| Tool | Purpose |
|---|---|
repo_map (action: importers) |
Find every file that imports from the target file |
repo_map (action: blast_radius) |
Find transitive dependents for high-risk renames |
symbols |
List the full exported API surface of the target file |
batch_symbols |
Bulk symbol extraction across multiple affected files |
search |
Find literal occurrences of the old symbol name across the codebase |
suggest_patch |
Preview changes before applying (dry-run) |
apply_patch |
Apply rename patches to consumer files |
edit |
Fallback for one-at-a-time rename edits when apply_patch is not suitable |
build_check (mode: typecheck) |
Verify the rename does not break compilation |
test_runner |
Run tests on affected files after rename |
Workflow
Step 1 — Identify the target
- Determine the file that exports the symbol and the symbol name to rename.
- If renaming a file itself, note the old path and the new path.
Step 2 — Discover consumers
- Run
repo_mapwith actionimportersandfileset to the target file path. This returns every file that imports from the target, with line numbers and import metadata. - If the rename is high-risk (the symbol is widely used or part of a core
utility), also run
repo_mapwith actionblast_radiusto understand transitive dependents.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · +1 lines 7a9b04f1d159
- 1mo ago First seen · 235 lines · 48 tokens per session scan A efe731dabab2
safe-rename is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (511 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 2,266 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.
tmux-real-user-testing
A real-user test workflow for Qwen Code's terminal interface, using tmux to drive the program and capture readable screen snapshots. tmux is a tool for running and observing terminal sessions.
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
deflake
Stabilize a flaky test with a minimal, assertion-preserving fix — never by weakening or deleting the check.