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 agentmods add commands/bluzername/claude-code-power-stack/rename-sessiongit clone --depth 1 https://github.com/bluzername/claude-code-power-stackWhat 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 | $0.00000 | $0.00255 |
| Opus 5 | $0.00000 | $0.00128 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
rename-session 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 2d 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
/rename-session - Name this session for easy retrieval
Analyze the current conversation and rename the session using a structured convention.
Convention
{project}-{type}-{descriptor}
project: Short slug derived from the working directory or conversation context (e.g., api, mobile, infra, docs)
type: One of:
feat- new featurefix- bug fixdebug- debugging sessionexplore- research/explorationreview- code reviewplan- planning/architectureresearch- deep researchcomms- communications
descriptor: 2-3 hyphenated words describing the specific task
Examples
api-feat-auth-flowmobile-fix-crash-on-logininfra-plan-k8s-migrationdocs-feat-api-reference
Steps
- Identify the project from the current working directory path or conversation topic
- Determine the task type from the user's request
- Create a concise 2-3 word descriptor
- Run:
/rename {project}-{type}-{descriptor}
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.
- 2d ago First seen · 35 lines · 0 tokens per session scan A 87acc17e8d75
rename-session is a command published in the GitHub repository bluzername/claude-code-power-stack (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 255 tokens. 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
release
Release a new version: bump version, update changelog, tag, push, and create a GitHub release.
checkout-branch
Switch to an existing branch by checking out its worktree, or creating one if needed.
benchmark
Run a TAU-bench evaluation end-to-end and present results.
create-pr
Create a pull request for the current branch against main.
kayba-agent-instructions
The kayba CLI interacts with the Kayba hosted API (https://use.kayba.ai). Auth: set KAYBAAPIKEY env var or pass --api-key to every command.
create-branch
Create a new git branch with an associated worktree following the project naming convention.