rename-drewgent

rename-drewgent is a skill for Claude Code, Codex from humanerd-drew/opencode-drewgent. It costs 29 tokens per session (688 once invoked), scanned A, original, MIT.

A repository-wide renaming procedure for changing the agent’s name in code, configuration, documentation, and related directories. It also updates the agent’s local paths and environment naming where required.

In plain words
What is it for?
Renaming agent directories, scripts, configuration entries, documentation references, and project titles across a large codebase.
Why use it?
Renaming an agent manually can leave stale references, broken paths, or mismatched configuration behind. A consistent procedure keeps those references aligned.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for gbrain. Also seen: mentions AGENTS.md; built for gbrain; mentions OpenCode.

Good fit Renaming agent directories, scripts, configuration entries, documentation references, and project titles across a large codebase.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/humanerd-drew/opencode-drewgent/rename-drewgent
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 humanerd-drew/opencode-drewgent --skill rename-drewgent
Clone the repo
git clone --depth 1 https://github.com/humanerd-drew/opencode-drewgent

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/rename-drewgent.svg)](https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/rename-drewgent)
Your own site
<a href="https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/rename-drewgent"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/rename-drewgent.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 688 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.00029 $0.00688
Opus 5 $0.00015 $0.00344
Sonnet 5 $0.00006 $0.00138
Haiku 4.5 $0.00003 $0.00069

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

Security

Grade A, and why

rename-drewgent 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 4d 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.

skills/software-development/rename-drewgent/SKILL.md · 67 lines

What it actually says

Rename {{AGENT_NAME}}

Replace all "{{AGENT_NAME_LOWER}}" references across the repo with your own agent name.

Convention

<yourname>gent — e.g., {{AGENT_NAME_LOWER}} → alexgent, saragent, devgent.

Usage

bash ~/.{{AGENT_NAME_LOWER}}/scripts/rename-{{AGENT_NAME_LOWER}}.sh "alexgent"

The script must:

  1. Replace {{AGENT_NAME_LOWER}}<new_name> in all .md, .py, .json, .jsonc, .yaml, .yml, .sh, .js, .html files (case-insensitive for filename patterns, case-sensitive for code references)
  2. Rename ~/.{{AGENT_NAME_LOWER}}~/.<new_name>gent (symlink or move)
  3. Update paths in opencode.jsonc and AGENTS.md
  4. Update the frontmatter title fields where "{{AGENT_NAME}}" appears as a project name
  5. Keep DREW_HOME env var or rename to <NAME>_HOME

What It Replaces

Pattern Example → New
Directory name ~/.{{AGENT_NAME_LOWER}}/~/.alexgent/
Config paths ~/.{{AGENT_NAME_LOWER}}/skills~/.alexgent/skills
Env vars DREW_HOMEALEX_HOME
Project name {{AGENT_NAME}}Alexgent (capitalized)
Code references {{AGENT_NAME_LOWER}}alexgent in inline paths
Script headers {{AGENT_NAME}} agent systemAlexgent agent system
opencode.jsonc skill paths, MCP paths
AGENTS.md all references

What It Does NOT Replace

  • The opencode CLI name (kept as-is)
  • External project names (opencode, gbrain, lazyweb)
  • Git remote URLs (must be changed separately)

Verification

After running, verify:

# No remaining old name
grep -r "{{AGENT_NAME_LOWER}}" ~/.alexgent/ --include="*.md" --include="*.py" --include="*.json" --include="*.jsonc" 2>/dev/null | head -5
# Should return nothing

# opencode loads correctly
opencode --version

# Config paths resolve
ls ~/.alexgent/opencode.jsonc
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. 4d ago First seen · 67 lines · 29 tokens per session scan A 7b508195dbd6

Subscribe to this mod's changes

rename-drewgent is a skill published in the GitHub repository humanerd-drew/opencode-drewgent (2 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 688 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-09-03.

Related

Other skills, from other repositories

itchio-new-game-hunt

Hunt for fresh browser-playable games on itch.io /newest that are worth building SEO arbitrage sites for. Crawls new releases, scores them by signals, produces ranked shortlist.

kennyzir/7deer_skills · 45 tokens

code-refactoring-assistant

Suggest and apply code refactorings to improve readability, maintainability, and code quality. Use this skill when improving existing code structure, eliminating code smells, applying design patterns, simplifying complex logic, extracting duplicated code, renaming for clarity, or preparing code for new features.…

ArabelaTso/Skills-4-SE · 81 tokens

function-class-generator

Generate complete, production-ready functions and classes from formal specifications, design descriptions, type signatures, or natural language requirements. Use this skill when implementing APIs from specifications, creating data structures from schemas, building classes from UML diagrams, generating code from…

ArabelaTso/Skills-4-SE · 71 tokens

scenario-generator

Generate comprehensive test scenarios, user stories, and acceptance criteria from requirements and specifications. Use this skill when planning testing efforts, writing user stories, creating test cases, documenting acceptance criteria, exploring edge cases, designing test coverage, or translating requirements into…

ArabelaTso/Skills-4-SE · 78 tokens

specification-generator

Generate formal specifications including preconditions, postconditions, invariants, and contracts from code or requirements. Use this skill when documenting APIs, creating formal verification annotations, defining function contracts, specifying class invariants, writing design-by-contract code, or preparing code for…

ArabelaTso/Skills-4-SE · 79 tokens

technical-debt-analyzer

Detect and analyze areas with high maintenance cost, poor design, or accumulated technical debt. Use this skill when reviewing codebases for quality issues, planning refactoring efforts, conducting code audits, assessing project health, identifying maintenance hotspots, or prioritizing technical improvements. Analyzes…

ArabelaTso/Skills-4-SE · 83 tokens