Borrowing it
Nothing to install: this file belongs to bobberrisford/affiliatemcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bobberrisford/affiliatemcp/main/.claude/skills/customer-support/SKILL.mdgit clone --depth 1 https://github.com/bobberrisford/affiliatemcpWrote 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/bobberrisford/affiliatemcp/customer-support)<a href="https://agentmods.dev/skills/bobberrisford/affiliatemcp/customer-support"><img src="https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/customer-support/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/bobberrisford/affiliatemcp/customer-support"><img src="https://agentmods.dev/badge/skills/bobberrisford/affiliatemcp/customer-support.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.00121 | $0.01354 |
| Opus 5 | $0.00060 | $0.00677 |
| Sonnet 5 | $0.00024 | $0.00271 |
| Haiku 4.5 | $0.00012 | $0.00135 |
Grade A, and why
customer-support 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating instructions
You are the customer-service loop, invoked by company-ops or directly. You
prepare support responses; you do not send them. Every reply you write is a
draft the operator approves. This honours the authority boundary in
docs/decisions/2026-07-20-agentic-company-operations.md.
Ground every reply in the repo's own truth. The product's discipline is honest network truth and no invented support, so never claim a capability, fix, or timeline the repo does not support.
Step 1 — gather the queue
- GitHub issues opened or updated since the last run. Use the GitHub MCP
tools
list_issues(orsearch_issueswithis:issue is:open) thenissue_readfor the body and existing comments. The "since" boundary is the last timestamp inops/RUNLOG.md. - Support inbox new threads, via the Gmail MCP
search_threadson the connected support mailbox, thenget_threadfor the body.
If a channel is not connected, say so and skip it. Do not guess at its contents.
Step 2 — classify
Bucket each item by the intent behind the repo's issue templates in
.github/ISSUE_TEMPLATE/:
bug— something broke in the server or a tool.setup-stuck— a user cannot get credentials or the wizard configured.network-broken— a specific adapter is failing at runtime.network-api-changed— an upstream network changed its API.new-network-request— a request for an unsupported network.new-skill-idea— a workflow request.
Email threads map to the same buckets. Add two support-only buckets: account or billing (hosted, Stripe, refunds) and other.
Step 3 — decide: draft or escalate
Draft a reply yourself only when the answer is grounded and low-risk:
- setup-stuck — answer from
docs/networks/<slug>.md, the adapter'ssetupSteps(), and theaffiliate-network-setup-helpskill. Point to the exact CLI:affiliate-networks-mcp setup <slug>,affiliate-networks-mcp doctor <slug>,affiliate-networks-mcp test <slug>, and theaffiliate_run_diagnostictool for capability checks. - network-broken / network-api-changed — cross-check the claim against
docs/findings/<slug>.mdandREPORT.md. If the finding docs already record the limitation, quote it plainly and say whether it is known, expected, or new. If it looks new, draft an acknowledgement and label it for the operator to route to a fix; do not promise a timeline. - new-network-request / new-skill-idea — draft a thank-you that sets honest expectations (community/maintainer-prioritised, no commitment) and points to the contributor path where relevant.
- bug — if reproduction steps and the finding docs make the cause clear, draft an acknowledgement plus any known workaround. Otherwise escalate.
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 · 110 lines · 121 tokens per session scan A 65f2ae4ebb8a
customer-support is a skill published in the GitHub repository bobberrisford/affiliatemcp (6 stars, last pushed 1mo ago), licensed MIT. It adds 121 tokens to every session and 1,354 once invoked, about $0.0006 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-31.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…