rename-prefix

A command that changes the prefix used in every issue ID and updates references to those IDs across the database. A prefix is the text before the issue number, such as "kw-" in "kw-42".

In plain words
What is it for?
Preview or apply a prefix change while automatically updating issue IDs, dependencies, and text references.
Why use it?
It lets a project adopt a clearer or shorter naming convention without leaving dependencies and written references pointing to old IDs.

Command

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.

agentmods
npx agentmods add commands/gastownhall/beads/rename-prefix
Clone the repo
git clone --depth 1 https://github.com/gastownhall/beads
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 141 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00007 $0.00141
Opus 5 $0.00003 $0.00071
Sonnet 5 $0.00001 $0.00028
Haiku 4.5 $0.00001 $0.00014

Measured yesterday against content hash 2e6a457dfe58, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rename-prefix 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 yesterday.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/beads/skills/beads/commands/rename-prefix.md · 24 lines

What it actually says

Rename the issue prefix for all issues in the database.

Updates all issue IDs and all text references across all fields.

Prefix Rules

  • Allowed: lowercase letters, numbers, hyphens
  • Must start with a letter
  • Must end with a hyphen (e.g., 'kw-', 'work-')

Usage

  • Preview: bd rename-prefix kw- --dry-run
  • Apply: bd rename-prefix kw-

Example: Rename from 'knowledge-work-' to 'kw-'

All dependencies and text references are automatically updated.

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. yesterday First seen · 24 lines · 7 tokens per session scan A 2e6a457dfe58

Subscribe to this mod's changes

rename-prefix is a command published in the GitHub repository gastownhall/beads (26,754 stars, last pushed yesterday), licensed MIT. It adds 7 tokens to every session and 141 once invoked, about $0.0000 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-30.