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 flurdy/agent-skills --skill name-sessiongit clone --depth 1 https://github.com/flurdy/agent-skillsWrote 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/flurdy/agent-skills/name-session)<a href="https://agentmods.dev/skills/flurdy/agent-skills/name-session"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/name-session/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/flurdy/agent-skills/name-session"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/name-session.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.00046 | $0.01062 |
| Opus 5.5 | $0.00018 | $0.00425 |
| Sonnet 5.5 | $0.00009 | $0.00212 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
name-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 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name session — propose a conventional session name
Build a <scope>-<descriptive> name from the current context and emit the active client's ready-to-paste rename command.
Important — client command and limitation
Harness selection comes from the current tool surface.
Never use the shell, PATH, filesystem, process list, or installed binaries to detect another client.
Treat the client as unknown when that surface does not conclusively identify Pi or Claude Code.
These rules are shared with /wrap-up and /handoffs; command printing is a proposal, not execution.
- It cannot rename the session for you. Slash commands emitted in model output are inert text; the user must enter the command in the client's command input.
- Pi: use
/name {session-name}. Never suggest/renameor/settings namein Pi. - Claude Code: use
/rename {session-name}. - If the client is unknown, state both commands rather than guessing.
Convention
<scope>-<descriptive>
- scope — the most specific identifier available, in priority order:
- Jira ticket from the branch name (e.g.
AB-1505) — keep its natural Jira case. - Active bead ID (e.g.
bd-123) if no ticket. - PR number (e.g.
pr-6563) if neither. - Omit the scope entirely if none apply — just use the descriptive part.
- Jira ticket from the branch name (e.g.
- descriptive — kebab-case, ≤4 words, the most specific noun phrase for what this session is doing.
rebase-pr-statusbeatsgit-stuff. Derive it from the conversation, not the branch (the branch already gives the scope).
Examples: AB-1505-rebase-pr-status, bd-412-flaky-test-hunt, pr-6563-review-comments, auth0-logout-investigation.
Instructions
1. Gather scope signals
Read the current branch with git rev-parse --abbrev-ref HEAD, using the repository wrapper where
required. Extract a ticket with [A-Z]+-\d+; detached HEAD is not a branch/ticket signal.
Without a ticket, prefer the bead explicitly identified as this session's work. If tracker validation
is needed, run ~/.agents/skills/next/scripts/next-select resolve <selector> and use the returned
owner for bd -C <directory> show <id>. Unavailable/ambiguous ownership drops that signal; do not scan
all in-progress claims and assume one belongs here. Existing known session context needs no fetch.
If neither applies and a PR is clearly this session's topic, use its known identity or a scoped
gh pr view --json number,title. No speculative PR request.
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.
- 4d ago Changed 097c394bf7d9
- 1mo ago Changed · +8 lines 95fedc500d7a
- 1mo ago Changed · -11 tokens per session 00456f6bf149
- 1mo ago First seen · 79 lines · 57 tokens per session scan A 5d8d5e3d1bc2
name-session is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,062 once invoked, about $0.0002 per session on Opus 5.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…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
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.
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…