contact-discovery

contact-discovery is a skill for Claude Code, Codex from orchidautomation/pluxx. It costs 18 tokens per session (1,600 once invoked), scanned A, original, MIT.

A contact-finding tool for identifying people and buyer-related information at selected companies. It can also organize matched people into contact lists.

In plain words
What is it for?
Use it to find contacts from names or LinkedIn URLs, create people lists, and add matched contacts to an existing list.
Why use it?
It reduces the manual work of finding relevant decision-makers and keeping prospect lists organized.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to find contacts from names or LinkedIn URLs, create people lists, and add matched contacts to an existing list.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orchidautomation/pluxx/contact-discovery
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 orchidautomation/pluxx --skill contact-discovery
Clone the repo
git clone --depth 1 https://github.com/orchidautomation/pluxx

Made for: Claude Code, Codex.

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-discovery

README.md
[![agentmods](https://agentmods.dev/badge/skills/orchidautomation/pluxx/contact-discovery/github.svg)](https://agentmods.dev/skills/orchidautomation/pluxx/contact-discovery)
Your own site
<a href="https://agentmods.dev/skills/orchidautomation/pluxx/contact-discovery"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/contact-discovery/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.

agentmods 80×15 button for contact-discovery

Your own site · 80×15
<a href="https://agentmods.dev/skills/orchidautomation/pluxx/contact-discovery"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/contact-discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,600 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 original No closer match found 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.00018 $0.01600
Opus 5.5 $0.00007 $0.00640
Sonnet 5.5 $0.00004 $0.00320
Haiku 4.5 $0.00002 $0.00160

Measured 2mo ago against content hash f66989954c99, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

contact-discovery 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 2mo 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.

example/sumble-plugin/skills/contact-discovery/SKILL.md · 225 lines

How it starts

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

Contact Discovery

Find people, contacts, and buyer-side context at the right accounts.

Tools In This Skill

AddContactsToList

Add people to an existing contact list.

Accepts Sumble person IDs. Returns how many were added,
how many were already on the list, and the list url.
Duplicates are silently skipped. Always surface the url
to the user so they can view the list in Sumble.

WORKFLOW — when a user provides names or LinkedIn URLs:
1. Call find_people to resolve them to Sumble person
   IDs.
2. Call add_contacts_to_list with the matched IDs
   (use the "id" field from each result).

If you already have Sumble person IDs (from a prior
API call), pass them directly as people_ids.

Args:
    reason: Why you are calling this tool.
    list_id: The contact list ID (from
        list_contact_lists or create_contact_list).
    people_ids: Sumble person IDs to add.

Inputs:

  • reason (string, required)
  • list_id (integer, required)
  • people_ids (array, required)

CreateContactList

Create a new contact list (people list).

Returns the new list's id, name, and url. Always
surface the url to the user so they can view the
list in Sumble. Use add_contacts_to_list to populate
it afterward.

WORKFLOW — when a user wants to build a people list:
1. Call find_people or find_related_people_to_person
   to get Sumble person IDs.
2. Call create_contact_list to make the list.
3. Call add_contacts_to_list with the person IDs.

If you already have Sumble person IDs (from a prior
API call), skip step 1 and use those IDs directly.

Always ask the user for the list name. If you have a
good guess, you can suggest it in the prompt.

Args:
    reason: Why you are calling this tool.
    name: Name for the new list.

Inputs:

  • reason (string, required)
  • name (string, required)

EnrichPerson

Enrich a person with contact information (email).

Read the full file on GitHub · 225 lines

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. 2mo ago First seen · 225 lines · 18 tokens per session scan A f66989954c99

Subscribe to this mod's changes

contact-discovery is a skill published in the GitHub repository orchidautomation/pluxx (5 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 1,600 once invoked, about $0.0001 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-09-03.

Related

contact-discovery compared with skills from other repositories

contact-discovery next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
contact-discoveryorchidautomation/pluxxSkill51mo agoMITA18Claude Code, Codex
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code