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 agentmods add skills/useconductor/conductor/conductor-mcpnpx skills add useconductor/conductor --skill conductor-mcpgit clone --depth 1 https://github.com/useconductor/conductorWrote 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/useconductor/conductor/conductor-mcp)<a href="https://agentmods.dev/skills/useconductor/conductor/conductor-mcp"><img src="https://agentmods.dev/badge/skills/useconductor/conductor/conductor-mcp.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00322 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
conductor-mcp 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 4d 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.
What it actually says
Conductor Integration Hub
Conductor connects Claude Code to 25+ external services through MCP tools.
When to use Conductor tools
- GitHub — list repos, create issues, check PRs, trigger Actions, manage releases
- Gmail — read, send, search, organize emails
- Google Calendar — check schedules, create events, find free time
- Google Drive — search, read, upload files
- Slack — send messages, read channels
- Notion — create pages, query databases, update notes
- Spotify — control playback, search tracks, manage playlists
- Vercel — check deployments, view project status
- HomeKit — control smart home devices, check sensors
- Weather — get current conditions and forecasts
- System — check CPU, memory, disk usage
- Network — ping hosts, check connectivity
- n8n — trigger automation workflows
- Calculator, Crypto, Hash, URL tools — utility operations
Setup
npm install && npm run build
conductor mcp setup
# Configure services
conductor google # Gmail, Calendar, Drive (OAuth)
conductor slack setup # Slack tokens
conductor plugins enable github
conductor plugins enable notion
conductor plugins enable spotify
Tool naming
All tools are prefixed with conductor_. Use conductor_status to check which plugins are active before attempting service-specific operations.
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.
- 4d ago First seen · 39 lines · 0 tokens per session scan A ecd4e8b8a831
conductor-mcp is a skill published in the GitHub repository useconductor/conductor (2 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 322 tokens. 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
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
github-secret-hunting
Find leaked API keys, tokens, and credentials in public GitHub repositories.
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries.
a11y-remediate
Use to produce a leader-facing remediation proposal from one or more /a11y-audit outputs plus team and product context. Translates audit findings into sprint plans, staffing asks, customer-facing language, compliance rollups, and critical-path analysis. Refuses to fabricate numbers, owners, or commitments beyond the…
github-image-upload
Upload local images and other files (PDF, zip, log, …) to GitHub and embed them in a pull request description, an issue, or a comment — producing canonical github.com/user-attachments URLs (private-repo uploads stay private). Use when asked to "attach a screenshot to the PR", "add an image to the PR description", "put…