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 customer-360git 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/customer-360)<a href="https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/customer-360"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/customer-360/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/customer-360"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/customer-360.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.00058 | $0.01619 |
| Opus 5 | $0.00029 | $0.00809 |
| Sonnet 5 | $0.00012 | $0.00324 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
customer-360 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 12d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer 360
Build a complete, unified view of any customer by aggregating their contact profile, conversation history, support topics, notes, and relevant knowledge base articles into a single structured summary.
Process
Step 1: Look Up the Contact
- If the user provides an email address, use
get_contactorlist_contactsto find the exact contact - If the user provides a name, use
list_contactsto search by name - If multiple contacts match, present the list and ask the user to confirm which one
- If no contact is found, report it and offer to create one using /contact-onboard
Step 2: Fetch Conversation History
- Use
list_conversationsfiltered to the contact to retrieve all their conversations - Sort conversations by most recent first
- For the most recent 5 conversations, use
get_conversationto read the full message threads - For older conversations, include only the subject, status, date, and assigned agent
Step 3: Identify Topics and Patterns
- Analyze the conversation threads to identify recurring topics (e.g., billing, setup, integrations, bugs)
- Note the customer's communication style and preferences (formal/informal, preferred channel)
- Identify any unresolved issues or pending follow-ups
- Track sentiment trajectory — is the customer generally satisfied, neutral, or frustrated?
Step 4: Search Knowledge Base
- Extract the top 3 topics from the customer's conversation history
- Use
search_knowledgefor each topic to find relevant KB articles - Include articles that could help resolve open issues or anticipate future questions
Step 5: Present Unified View
Compile everything into the structured profile card format below.
Output Format
Customer 360: [Full Name]
Profile
- Email: [email]
- Phone: [phone or "Not provided"]
- Company: [company or "Not provided"]
- Tags: [list of tags]
- Created: [date first seen]
- Last active: [date of most recent conversation]
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.
- 12d ago First seen · 137 lines · 58 tokens per session scan A 01757fb03960
customer-360 is a skill published in the GitHub repository jonny-1812/corebee-mcp-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,619 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
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…
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…
Zendesk Automation
Automate customer support workflows with Zendesk ticket management, routing, and analytics.
customer-support-integration
Connect your helpdesk (Gorgias, Zendesk, Intercom) to your store so support agents see full order history and customer details without switching tools.