Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Jamaalx/claude-chat-namer/plugin install chat-namerWrote 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/jamaalx/claude-chat-namer/resume)<a href="https://agentmods.dev/skills/jamaalx/claude-chat-namer/resume"><img src="https://agentmods.dev/badge/skills/jamaalx/claude-chat-namer/resume/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/jamaalx/claude-chat-namer/resume"><img src="https://agentmods.dev/badge/skills/jamaalx/claude-chat-namer/resume.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.00013 | $0.00251 |
| Opus 5 | $0.00006 | $0.00125 |
| Sonnet 5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
resume 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.
What it actually says
Help the user find and resume a previous Claude Code conversation.
Step 1: If the user provided arguments (e.g. /chat-namer:resume wolt), search for it:
node ${CLAUDE_PLUGIN_ROOT}/scripts/cli.js search "$ARGUMENTS"
If no arguments, list recent conversations:
node ${CLAUDE_PLUGIN_ROOT}/scripts/cli.js list
Step 2: Show the results and ask the user which conversation they want to resume.
Step 3: Once they pick one, give them the exact command to run in a NEW terminal:
claude --resume <full-uuid>
Important notes:
- The
claude --resumecommand must be run in a NEW terminal session, not inside this one - Always provide the FULL UUID (not just the prefix) so the resume command works correctly
- You can also mention they can use
claude --resumewithout arguments to open the interactive picker - If they want to continue THIS session, they don't need resume - they're already in it
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 First seen · 30 lines · 13 tokens per session scan A 7e006b4328f9
resume is a skill published in the GitHub repository Jamaalx/claude-chat-namer (4 stars, last pushed 11d ago), licensed MIT. It adds 13 tokens to every session and 251 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-08-31.
Other skills, from other repositories
profile
Read the user's ENTIRE Claude Code message history with a multi-agent workflow, mine the working preferences that recur across almost all their tasks, verify each against the whole corpus, and distill them into a CLAUDE.md block so they never have to repeat them. Language-agnostic. Triggers: 'analyze how I use…
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
tokf-discover
Find missed token savings by scanning AI coding session files for commands that ran without tokf filtering.
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
handoff
Write a portable, secret-scrubbed handoff doc so this work can continue in any AI tool or on any machine. Use when saying "handoff", "running out of tokens", or "continue elsewhere".
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…