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 jtsternberg/claude-plugins --skill auto-renamegit clone --depth 1 https://github.com/jtsternberg/claude-pluginsWrote 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/jtsternberg/claude-plugins/auto-rename)<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/auto-rename"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/auto-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/jtsternberg/claude-plugins/auto-rename"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/auto-rename.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00052 | $0.02311 |
| Opus 5 | $0.00026 | $0.01156 |
| Sonnet 5 | $0.00010 | $0.00462 |
| Haiku 4.5 | $0.00005 | $0.00231 |
Grade A, and why
auto-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 9d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-rename cmux tabs & workspaces
Summarize what a cmux tab (surface) or workspace is actually doing, generate a concise helpful name, and apply it with cmux rename-tab / cmux rename-workspace.
REQUIRED BACKGROUND: the companion using-cmux-cli skill covers handle formats, identify, tree, read-screen, and its gotchas (especially the Claude Code ghost-autosuggest trap). This skill assumes that vocabulary.
Current context (resolved at skill load)
cmux identify --json --id-format both 2>/dev/null || echo '{"error":"cmux identify failed — outside cmux or socket unreachable"}'
--id-format both gives each entry its stable UUID (*_id) alongside its positional *_ref. Target by the UUID.
caller.*— where this agent runs. Default target for "rename this tab/workspace".focused.*— where the user is looking. Target this when they say "the tab I'm looking at".
Step 1 — Resolve the target(s)
| User says | Target |
|---|---|
| "rename this tab" / "auto-name my tab" | caller.tab_id (UUID) |
| "rename this workspace" | caller.workspace_id (UUID) |
| "rename both" / bare "auto-rename" | caller tab and caller workspace |
| "the tab/workspace I'm looking at" | focused.* |
| "the tab running the build" / a named workspace | find it: cmux tree --all --json + jq, or the using-cmux-cli find-surface.sh helper |
| "rename everything here" / "all tabs in this workspace" / "fix all the tab names" / bare "all" | scoped batch — every tab under caller.workspace_id, plus the workspace itself (see Batch mode) |
Scope is always the current workspace, never all of them. There is deliberately no "rename every workspace" mode — a mass rename across many workspaces is disruptive and unwanted. "all" means "everything in this workspace."
Gotcha (verified): cmux tree --workspace <ref> --json ignores the workspace filter and returns the whole tree — grabbing the first surface from it targets the wrong workspace and rename-tab fails with not_found: Tab not found. Either use the plain-text cmux tree --workspace <ref> (which is scoped) or filter the JSON yourself by UUID: cmux tree --all --json --id-format both | jq --arg w "<ws-uuid>" '.. | objects | select(.id==$w)'.
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.
- 9d ago First seen · 129 lines · 52 tokens per session scan A 33d9e08e30c0
auto-rename is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 2,311 once invoked, about $0.0003 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-31.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.