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 add-contactgit 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/add-contact)<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/add-contact"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/add-contact.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.00020 | $0.00521 |
| Opus 5 | $0.00010 | $0.00260 |
| Sonnet 5 | $0.00004 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
hotline-add-contact 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.
What it actually says
Hotline: Add Contact
Register a workspace in dirmap so it can be found by hotline-dial during workspace resolution.
Arguments
- $1 (slug): The short name/alias for this workspace (e.g.,
blog,coaching,frontend). If not provided, ask the user. - $2 (path): The workspace path to register. Defaults to the current working directory if not provided.
Steps
1. Determine Slug and Path
SLUG="$1 or ask the user"
TARGET_PATH="$2 or $(pwd)"
If no slug was provided, ask the user:
What slug should I register this workspace under? (e.g., "blog", "coaching", "frontend")
Resolve the path to its canonical form:
TARGET_PATH=$(realpath "$TARGET_PATH")
2. Check for Existing Entry
Before adding, check if this slug already exists:
dirmap get "$SLUG" 2>/dev/null || dirmap-fallback.sh get "$SLUG" 2>/dev/null
If it exists and points to a different path, confirm with the user:
"$SLUG" is already registered at
/existing/path. Overwrite with$TARGET_PATH?
3. Register the Workspace
if command -v dirmap >/dev/null 2>&1; then
dirmap add "$SLUG" "$TARGET_PATH"
elif [[ ! -f "$HOME/.dirmap.json" ]]; then
jq -n --arg slug "$SLUG" --arg path "$TARGET_PATH" \
'{($slug): $path}' > "$HOME/.dirmap.json"
else
jq --arg slug "$SLUG" --arg path "$TARGET_PATH" \
'. + {($slug): $path}' "$HOME/.dirmap.json" > "$HOME/.dirmap.json.tmp" \
&& mv "$HOME/.dirmap.json.tmp" "$HOME/.dirmap.json"
fi
4. Confirm
Registered $SLUG →
$TARGET_PATH. Other agents can now find this workspace withhotline-dial.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 64 lines · 20 tokens per session scan A bcccd9820b66
hotline-add-contact is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 521 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…