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 orchidautomation/pluxx --skill contact-discoverygit clone --depth 1 https://github.com/orchidautomation/pluxxWrote 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/orchidautomation/pluxx/contact-discovery)<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.
<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>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.00018 | $0.01600 |
| Opus 5 | $0.00009 | $0.00800 |
| Sonnet 5 | $0.00004 | $0.00320 |
| Haiku 4.5 | $0.00002 | $0.00160 |
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 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 — 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).
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 · 225 lines · 18 tokens per session scan A f66989954c99
contact-discovery is a skill published in the GitHub repository orchidautomation/pluxx (5 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 1,600 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-09-03.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…