Borrowing it
Nothing to install: this file belongs to research-developer/iterm-mcp-claude-agency. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/research-developer/iterm-mcp-claude-agency/main/.claude/commands/session-ids.mdgit clone --depth 1 https://github.com/research-developer/iterm-mcp-claude-agencyWrote 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/commands/research-developer/iterm-mcp-claude-agency/session-ids)<a href="https://agentmods.dev/commands/research-developer/iterm-mcp-claude-agency/session-ids"><img src="https://agentmods.dev/badge/commands/research-developer/iterm-mcp-claude-agency/session-ids/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/commands/research-developer/iterm-mcp-claude-agency/session-ids"><img src="https://agentmods.dev/badge/commands/research-developer/iterm-mcp-claude-agency/session-ids.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.00012 | $0.00296 |
| Opus 5 | $0.00006 | $0.00148 |
| Sonnet 5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
session-ids 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.
What it actually says
Session IDs
Display session identification information for debugging and correlation purposes.
Instructions
-
First, get the iTerm session information using the
check_session_statustool (orlist_sessionswith format="json" for multiple sessions) -
Display the following information:
- iTerm Session ID (
id) - The native iTerm2 session identifier (UUID format) - Persistent ID (
persistent_id) - Persistent session ID for reconnection across restarts - Session Name (
name) - Human-readable session name - Agent Name (
agent) - Associated agent name (if registered) - Active Status (
is_active) - Whether this is the currently active session
- iTerm Session ID (
-
For the Claude Code session ID, check the environment variable:
- Run:
echo $CLAUDE_SESSION_IDin the terminal to get the Claude session ID - This is set by iTerm MCP hooks when entering a repository
- Run:
Example Output Format
Present the results clearly:
Session IDs
-----------
iTerm Session ID: ABC123-DEF456-789...
Persistent ID: persistent-uuid-here...
Session Name: main
Agent: worker-1
Active: Yes
Claude Code Session: (check $CLAUDE_SESSION_ID in terminal)
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 · 39 lines · 12 tokens per session scan A 3808d87c33a8
session-ids is a command published in the GitHub repository research-developer/iterm-mcp-claude-agency (4 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 296 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.