Borrowing it
Nothing to install: this file belongs to anton-abyzov/vskill. 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/anton-abyzov/vskill/main/.claude/skills/marketing/slack-messaging/SKILL.mdgit clone --depth 1 https://github.com/anton-abyzov/vskillWrote 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/anton-abyzov/vskill/slack-messaging)<a href="https://agentmods.dev/skills/anton-abyzov/vskill/slack-messaging"><img src="https://agentmods.dev/badge/skills/anton-abyzov/vskill/slack-messaging.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 150 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00199 | $0.02699 |
| Opus 5 | $0.00100 | $0.01350 |
| Sonnet 5 | $0.00040 | $0.00540 |
| Haiku 4.5 | $0.00020 | $0.00270 |
Grade A, and why
slack-messaging 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 8d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack Messaging
Read, send, search, draft, and schedule Slack messages across channels and threads. This skill wraps the Slack MCP tools with clear workflows and -- critically -- enforces context boundaries: thread conversations keep their context within a single session, while each new channel-level conversation gets a fresh session.
Why Context Boundaries Matter
Slack conversations have natural scoping. A thread is one continuous discussion -- if you lose context mid-thread, your replies become disjointed and unhelpful. But two unrelated messages in a channel are separate conversations -- mixing their context causes confusion and information leakage between topics.
This skill enforces these boundaries so your Slack interactions stay coherent:
- Thread = one session. All replies within the same thread share context. You remember what was said earlier in the thread and can reference it.
- New channel message = new session. Each top-level message you respond to in a channel starts fresh. No carryover from previous conversations.
Session Management Rules
When to Keep the Same Session (Thread Continuity)
Stay in the same Claude Code session when:
- You are replying to a thread and need to send a follow-up reply in that same thread
- The user asks you to continue a conversation you already started in a thread
- You are reading and responding to multiple messages within a single thread
- The user says things like "reply again", "follow up", "add to that thread", "also mention..."
In practice: if you have a thread_ts and you're sending another message with the same thread_ts, you are in the same conversation. Keep your context.
When to Start a New Session (Channel Isolation)
Start a new Claude Code session (fresh context) when:
- The user asks you to respond to a different top-level message in a channel
- You move from one channel conversation to an unrelated one
- The user asks you to "check Slack" or "read messages" in a channel -- each message that needs a response is its own session
- The user says things like "now respond to that other message", "handle the next one", "what about the message from [someone else]"
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.
- 8d ago First seen · 247 lines · 199 tokens per session scan A 456e67e42972
slack-messaging is a skill published in the GitHub repository anton-abyzov/vskill (45 stars, last pushed yesterday), licensed MIT. It adds 199 tokens to every session and 2,699 once invoked, about $0.0010 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-30.
Other skills, from other repositories
help-flow
Help about Rosetta: explains capabilities and usage.
external-lib-flow
Workflow for onboarding an external private library so AI can use it without source access.
modernization-flow
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
coding-flow
Light coding workflow: features, fixes, refactors, unit tests, etc.; scales small to large.
coding-agents-prompting-flow
Workflow for authoring and adapting AI-agent prompts: skills, agents, workflows, rules, etc.