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 jonny-1812/corebee-mcp-skills --skill contact-onboardgit clone --depth 1 https://github.com/jonny-1812/corebee-mcp-skillsWrote 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/jonny-1812/corebee-mcp-skills/contact-onboard)<a href="https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/contact-onboard"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/contact-onboard/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/jonny-1812/corebee-mcp-skills/contact-onboard"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/contact-onboard.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.00062 | $0.01172 |
| Opus 5 | $0.00031 | $0.00586 |
| Sonnet 5 | $0.00012 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
contact-onboard 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 13d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contact Onboarding
Streamline adding new contacts with duplicate detection, bulk operations, updates, and contextual notes.
Workflow Modes
1. Single Onboard
Use when the user provides one contact to add.
- Check for duplicates using
list_contactswithsearchset to the email or name - If no duplicate found, create the contact using
create_contactwith all provided details - If the user provides context about the contact (e.g., "interested in Pro plan"), add a note using
add_contact_note - Confirm creation by showing the contact details
2. Bulk Onboard
Use when the user provides multiple contacts at once (a list, CSV paste, or describes several people).
- Parse all contacts from the input — extract name and email for each
- For each contact, check for duplicates using
list_contactswithsearch - Create each non-duplicate contact using
create_contact - Add notes to any contacts that had contextual info attached
- Present a summary table: created, skipped (duplicate), and any errors
3. Update Existing
Use when the user wants to modify an existing contact's details.
- Look up the contact using
list_contactswithsearchorget_contactif ID is known - If not found, inform the user and offer to create a new contact instead
- Apply changes using
update_contactwith only the fields that need changing - Confirm by showing the updated contact details
4. Delete Contact
Use when the user wants to remove a contact (e.g., test data, duplicate cleanup).
- Look up the contact using
list_contactswithsearchorget_contact - Confirm with the user before deleting — show the contact name and email
- Delete using
delete_contact - Confirm deletion
Information Gathering
If the user provides partial info, ask for:
- Name (required) — full name
- Email (recommended) — for communication and duplicate detection
- Phone (optional) — only if relevant
Do not ask for fields the user has not mentioned. Keep it lightweight.
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.
- 13d ago First seen · 122 lines · 62 tokens per session scan A 865beb4a22f1
contact-onboard is a skill published in the GitHub repository jonny-1812/corebee-mcp-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 1,172 once invoked, about $0.0003 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-30.
Other skills, from other repositories
Zendesk Automation
Automate customer support workflows with Zendesk ticket management, routing, and analytics.
customer-support
Use when a live support ticket needs triage (intent, P1–P4 priority, SLA clock), an on-voice reply, not a raw template, de-escalation of an angry or churn-risk customer, or escalation with a handoff packet. NOT the help-center article it links to (that is technical-writing), a win-back program (retention), or the…
customer-support-expert
Build comprehensive customer support systems including ticketing, knowledge management, SLA tracking, and customer satisfaction analytics. Use when the user mentions helpdesk or service desk, ticketing, SLA targets, knowledge bases, escalation workflows, CSAT/NPS, or customer success operations.
deskcrew-support
Run a customer support desk on DeskCrew. Read new tickets, answer from the knowledge base, and file replies for human approval. Use when handling customer support. Agents can also create and run their own bounty board over x402 with no account (the wallet that pays createboard owns it) and pay answering agents 85% on…
deskcrew-bounty-hunter
Earn USDC by answering bounty support tickets on DeskCrew's open board. Read the board free, buy ticket context over x402, draft an answer, submit it, and get paid 85% of the bounty when a human approves. Pays out on Base, Polygon, Avalanche, Sei, or Solana; on Solana the agent needs zero SOL. Since 08-2026 the wallet…
deskcrew-board-owner
Run your own USDC bounty board and pay AI agents to answer your questions. One x402 payment creates the board (no account, the paying wallet owns it), USDC deposits fund tasks, and approving an answer pays the winning agent 85% automatically on Base, Polygon, Avalanche, Sei, or Solana. Use when asked to delegate work…