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 jtsternberg/claude-plugins/plugin install hotlineWrote 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/caller-id)<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/caller-id"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/caller-id.svg" alt="Measured on agentmods" 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.00023 | $0.00821 |
| Opus 5 | $0.00012 | $0.00411 |
| Sonnet 5 | $0.00005 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
hotline-caller-id 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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hotline: Session ID
Discover your own session ID. On current Claude Code (>= 2.1.132) this resolves natively in a single call; older clients fall back to Hotline's legacy fingerprint-and-grep discovery.
Script Paths
Resolve plugin paths first:
# Codex: this path resolves under Claude Code; substitute the directory containing this plugin.
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}"
eval "$(bash "$PLUGIN_ROOT/scripts/paths.sh")"
This sets HOTLINE_SCRIPTS (and others). Use $HOTLINE_SCRIPTS in all script references below.
Resolve Identity
One Bash call resolves identity on every current harness:
# Codex: this path resolves under Claude Code; substitute the directory containing this plugin.
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}"
eval "$(bash "$PLUGIN_ROOT/scripts/paths.sh")" && \
bash "$HOTLINE_SCRIPTS/session-init.sh"
The script checks, in order: an explicit HOTLINE_CALLER_SESSION_ID override, Claude Code's native CLAUDE_CODE_SESSION_ID (exported into every Bash subprocess since 2.1.132), Codex's CODEX_THREAD_ID, and only then the legacy fingerprint path.
Parse the JSON output:
{"status": "cached", "session_id": "...", "caller_kind": "native"}— done. This is the normal outcome on current Claude Code (caller_kindmay also beoverrideorcodex; a legacy fingerprint cache hit omits the field entirely). Skip to Report.{"status": "planted", "fingerprint": "..."}— legacy client fallback (pre-2.1.132 Claude, or a stripped environment). Save the fingerprint and proceed to Legacy Step 2 in a separate tool call.{"status": "error", "message": "..."}— report the error to the user. Discovery failed.
Legacy Step 2: Discover from Fingerprint
Only needed when the previous call returned planted. This MUST be a separate Bash tool call — the fingerprint is written into the transcript when the first tool call returns, so it won't exist yet if both steps run in one shell.
# Codex: this path resolves under Claude Code; substitute the directory containing this plugin.
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}"
eval "$(bash "$PLUGIN_ROOT/scripts/paths.sh")" && \
bash "$HOTLINE_SCRIPTS/session-init.sh" discover "<fingerprint>"
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.
- 8d ago First seen · 76 lines · 23 tokens per session scan A 45fbbb986e95
hotline-caller-id is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 821 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…