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.
/plugin marketplace add nileshpatil6/telegram-slack-mcpnpx agentmods add plugins/nileshpatil6/telegram-slack-mcp/slackgit clone --depth 1 https://github.com/nileshpatil6/telegram-slack-mcpWrote 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/plugins/nileshpatil6/telegram-slack-mcp/slack)<a href="https://agentmods.dev/plugins/nileshpatil6/telegram-slack-mcp/slack"><img src="https://agentmods.dev/badge/plugins/nileshpatil6/telegram-slack-mcp/slack.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
slack 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 2d 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
{
"name": "slack",
"description": "Read and post across all your Slack workspaces from Claude",
"version": "0.5.1",
"author": { "name": "nileshpatil6", "url": "https://github.com/nileshpatil6" },
"homepage": "https://github.com/nileshpatil6/telegram-slack-mcp",
"repository": "https://github.com/nileshpatil6/telegram-slack-mcp",
"license": "MIT",
"keywords": ["slack", "messaging", "mcp"]
}
What it installs
The manifest is a name and a version. 1 MCP server travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
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.
- 2d ago Changed a33566e8e53b
- 5d ago First seen · 11 lines scan A 4c21f7cbaa9b
slack is a plugin published in the GitHub repository nileshpatil6/telegram-slack-mcp (0 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
full-process
Drives a full feature-development workflow (clarify -> design -> plan -> execute -> PR -> test) over Slack via the claude-slack-bridge daemon. Ships /process-setup for one-time per-repo configuration and /process for clarification + handoff to the daemon's workflow engine.
telethon-plus
HTTP + MCP control plane over a real Telegram MTProto userbot (Telethon) — send/read/edit/delete/forward messages, dialogs, entities, media, chat admin, and polls, plus an incoming-message webhook.
rustunnel
Expose local services via secure tunnels. Create public HTTPS/TCP/UDP URLs, peer-to-peer tunnels, and load-balanced pools for webhooks, demos, and AI agent workflows.
secedgar-mcp-server
Query SEC EDGAR filings, XBRL financials, and company data through MCP. STDIO & Streamable HTTP.
cdc-health-mcp-server
Search and query CDC public health data — mortality, vaccinations, surveillance, behavioral risk (Socrata SODA API) via MCP. STDIO or Streamable HTTP.
claude-webcache
Cross-session WebFetch cache for Claude Code. WebFetches disappear after 15 minutes — claude-webcache makes them persist.