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 Livus-AI/Skills-MCP --skill slack-messagegit clone --depth 1 https://github.com/Livus-AI/Skills-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/skills/livus-ai/skills-mcp/slack-message)<a href="https://agentmods.dev/skills/livus-ai/skills-mcp/slack-message"><img src="https://agentmods.dev/badge/skills/livus-ai/skills-mcp/slack-message/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/livus-ai/skills-mcp/slack-message"><img src="https://agentmods.dev/badge/skills/livus-ai/skills-mcp/slack-message.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.00030 | $0.00475 |
| Opus 5 | $0.00015 | $0.00237 |
| Sonnet 5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
slack-message 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 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.
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
Slack Message Skill
Send messages to Slack channels using incoming webhooks.
Prerequisites
You need a Slack Incoming Webhook URL. To get one:
- Go to your Slack workspace's App Directory
- Search for "Incoming Webhooks" and add it
- Choose a channel and copy the webhook URL
- Either set
SLACK_WEBHOOK_URLenvironment variable or pass it as a parameter
Available Scripts
post.py- Post a message to Slack
How to Use
Basic Usage
execute_skill_script("slack-message", "post.py", {
"message": "Hello from Skills MCP!"
})
With Webhook URL
execute_skill_script("slack-message", "post.py", {
"webhook_url": "https://hooks.slack.com/services/...",
"message": "Deployment completed successfully! ✅"
})
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
message |
string | Yes | The message text to post |
webhook_url |
string | No | Slack webhook URL (or set SLACK_WEBHOOK_URL env var) |
channel |
string | No | Override the default channel |
username |
string | No | Override the bot username |
Example Response
Success:
{
"status": "success",
"message": "Message posted to Slack successfully",
"timestamp": "2024-12-30T12:00:00"
}
Error (no webhook):
{
"status": "error",
"message": "No webhook_url provided and SLACK_WEBHOOK_URL not set"
}
Security Notes
- Never commit webhook URLs to version control
- Use environment variables for sensitive credentials
- Webhook URLs should be treated as secrets
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 80 lines · 30 tokens per session scan A e29b9b60a866
slack-message is a skill published in the GitHub repository Livus-AI/Skills-MCP (2 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 475 once invoked, about $0.0002 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…