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 matteotitta/genesys-skills --skill connect-mcpgit clone --depth 1 https://github.com/matteotitta/genesys-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/matteotitta/genesys-skills/connect-mcp)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/connect-mcp"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/connect-mcp/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/matteotitta/genesys-skills/connect-mcp"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/connect-mcp.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.00129 | $0.01791 |
| Opus 5 | $0.00064 | $0.00896 |
| Sonnet 5 | $0.00026 | $0.00358 |
| Haiku 4.5 | $0.00013 | $0.00179 |
Grade C, and why
connect-mcp scanned grade C with 2 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 11d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Promote to tier A (`~/.claude/settings.json`, always-on) only after 2–4 weeks of proven >50%-session use and auth stability, and document the promotion in MEMORY.md. Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
- **Extrovert** (project-scope HTTP): `.claude/.mcp.json` entry → `https://mcp.goextrovert.com`, `Authorization: Bearer ${EXTROVERT_API_KEY}`, key in `.claude/apis/extrovert-api-key.txt`, introspection + seed via `.claud How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connect an MCP
The step-by-step procedure for adding any custom MCP to Claude. The policy — when an MCP earns always-on status versus project-scope versus deferred — lives in mcp-on-demand.md. This runbook is the procedure that policy implies, with Extrovert (project-scope HTTP) and Spider (local stdio) as worked examples.
Born from the /steal of Gojiberry's "Connect Claude to LinkedIn via MCP" playbook: the generic "add a custom connector" mechanics were worth keeping; the vendor connector itself was not. See .claude/discovery/0626-gojiberry-linkedin-mcp-steal-analysis.md.
When to use
- Adding a new MCP server (any client, any service)
- A
/stealor MCP-registry pass surfaces an MCP worth trying - Re-enabling a demoted MCP into a specific workspace
Process
Step 1 — Choose the source
| Source | Use when | Tier it implies |
|---|---|---|
| Official plugin | An official plugin exists (e.g., exa@claude-plugins-official) |
C (deferred) — zero startup cost |
| Community MCP | A maintained community server fits | B (project-scope) to start |
| Custom HTTP | A hosted server with an API key (e.g., Extrovert) | B (project-scope) |
| Local stdio | A local binary (e.g., Spider spider-mcp) |
B (project-scope) |
Step 2 — Decide the tier
Follow the mcp-on-demand.md decision tree, do not restate it:
- Official plugin exists → install as plugin (tier C, deferred).
- Otherwise →
claude mcp add --scope project(tier B). This is the default for anything new. - Promote to tier A (
~/.claude/settings.json, always-on) only after 2–4 weeks of proven >50%-session use and auth stability, and document the promotion in MEMORY.md.
Default to tier B/C. Never add a new MCP to user-scope "to have it ready" — every always-on MCP adds a handshake and a failure mode to every session.
Step 3 — Wire credentials
For an MCP needing a key:
- Drop the key in a gitignored file:
.claude/apis/{service}-api-key.txt. - The SessionStart hook
.claude/hooks/load-mcp-env.shexports it as{SERVICE}_API_KEY(kebab → snake, uppercase). Soextrovert-api-key.txt→$EXTROVERT_API_KEY. - Reference the env var in the MCP config — never hard-code the key.
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.
- 11d ago First seen · 131 lines · 129 tokens per session scan C fb61cffd68e4
connect-mcp is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 1,791 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (reads agent configuration directories, reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
gingiris-go-global
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles.…
gr-competitor-research
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.