contact-research

contact-research is a skill for Claude Code from common-room/claude-plugin. It costs 48 tokens per session (1,157 once invoked), scanned A, a copy of contact-research, Apache-2.0.

A contact lookup and research workflow using Common Room, a system that collects information about potential customers and their activity. It can search by email, social handle, or a person's name and company.

In plain words
What is it for?
Use it to identify a contact, review their activity, check whether they may be an interested lead, or answer a question about a specific person.
Why use it?
It avoids guessing who a person is and gathers their available activity, scores, website visits, and customer-record details in one profile.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the common-room plugin — 6 skills, 2 commands, 1 MCP server shipped together

Good fit Use it to identify a contact, review their activity, check whether they may be an interested lead, or answer a question about a specific person.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/common-room/claude-plugin/contact-research
Install

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.

Any agent
npx skills add common-room/claude-plugin --skill contact-research
Clone the repo
git clone --depth 1 https://github.com/common-room/claude-plugin

Made for: Claude Code.

Or install common-room, the plugin that ships this one along with the rest of its 6 skills, 2 commands, 1 MCP server.

Wrote 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.

agentmods badge for contact-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/common-room/claude-plugin/contact-research.svg)](https://agentmods.dev/skills/common-room/claude-plugin/contact-research)
Your own site
<a href="https://agentmods.dev/skills/common-room/claude-plugin/contact-research"><img src="https://agentmods.dev/badge/skills/common-room/claude-plugin/contact-research.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,157 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.01157
Opus 5 $0.00024 $0.00579
Sonnet 5 $0.00010 $0.00231
Haiku 4.5 $0.00005 $0.00116

Measured 7d ago against content hash 3c01f6465244, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

contact-research 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 7d 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.

Origin

This is a copy

100% identical to contact-research — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/contact-research/SKILL.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Contact Research

Retrieve a comprehensive contact profile from Common Room. Supports lookup by email, social handle, or name + company. Returns enriched data including activity history, Spark, scores, website visits, and CRM fields.

Step 1: Locate the Contact

Common Room supports multiple lookup methods — use whichever the user has provided:

What the user gives Lookup method
Email address Look up by email (most reliable)
LinkedIn, Twitter/X, or GitHub handle Look up by social handle — specify handle type explicitly
Name + company Identity resolution by name + org domain; present matches if ambiguous
Name only Search by name; if multiple matches, show a brief list and ask the user to confirm

If no match is found, respond: "Common Room doesn't have a record for this person." Do not speculate or fabricate profile data.

Step 2: Fetch Contact Fields

Use the Common Room object catalog to see available field groups and their contents. For full profiles, request all groups. For targeted questions, request only what's relevant.

Key field groups to know about:

  • Scores — always return as raw values or percentiles, never labels
  • Recent activity — use Contact Initiated filter (last 60 days) for their actions, not your team's
  • Website visits — total count + specific pages (last 12 weeks)
  • Spark — retrieve all Sparks when tracking engagement evolution over time

Step 3: Run Spark Enrichment (If Available)

If Spark is available, use it. Spark provides:

  • Professional background and job history
  • Social presence and influence signals
  • Persona classification: Champion, Economic Buyer, Technical Evaluator, End User, or Gatekeeper
  • Inferred role in the buying process

If Spark is unavailable but real activity data exists (recent actions, website visits, community engagement), infer a persona from those signals. If neither Spark nor activity data is available, classify as Unknown — do not guess a persona from title alone.

Read the full file on GitHub · 130 lines

Files

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.

Changes

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.

  1. 7d ago First seen · 130 lines · 48 tokens per session scan A 3c01f6465244

Subscribe to this mod's changes

contact-research is a skill published in the GitHub repository common-room/claude-plugin (3 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 1,157 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to contact-research, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 103 tokens

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…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens