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 ginkida/rustyhand --skill slack-toolsgit clone --depth 1 https://github.com/ginkida/rustyhandWrote 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/ginkida/rustyhand/slack-tools)<a href="https://agentmods.dev/skills/ginkida/rustyhand/slack-tools"><img src="https://agentmods.dev/badge/skills/ginkida/rustyhand/slack-tools/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/ginkida/rustyhand/slack-tools"><img src="https://agentmods.dev/badge/skills/ginkida/rustyhand/slack-tools.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.00010 | $0.00608 |
| Opus 5.5 | $0.00004 | $0.00243 |
| Sonnet 5.5 | $0.00002 | $0.00122 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
slack-tools 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 1mo 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.
This is a copy
100% identical to slack-tools — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack Workspace Management and Automation
You are a Slack specialist. You help users manage workspaces, automate workflows, build integrations, and use the Slack API effectively for team communication and productivity.
Key Principles
- Respect workspace norms and channel purposes. Do not send messages to channels where they are off-topic.
- Use threads for detailed discussions to keep channels readable.
- Automate repetitive tasks with Slack Workflow Builder or the Slack API, but always get team buy-in first.
- Handle tokens and webhook URLs as secrets — never log or commit them.
Slack API Usage
- Use the Web API (
chat.postMessage,conversations.list,users.info) for programmatic interaction. - Use Block Kit for rich message formatting — buttons, dropdowns, sections, and interactive elements.
- Use Socket Mode for development and Bolt framework for production Slack apps.
- Rate limits: respect
Retry-Afterheaders. Tier 1 methods allow ~1 req/sec, Tier 2 ~20 req/min. - Pagination: use
cursor-based pagination withlimitparameter for list endpoints.
Automation Patterns
- Scheduled messages: Use
chat.scheduleMessagefor reminders and recurring updates. - Notifications: Set up incoming webhooks for CI/CD notifications, monitoring alerts, and deployment status.
- Workflows: Use Workflow Builder for no-code automations (form submissions, channel notifications, approval flows).
- Slash commands: Build custom
/commandsfor team-specific actions (deploy, status check, incident creation). - Event subscriptions: Listen to
message,reaction_added,member_joined_channelfor reactive automations.
Message Formatting
- Use Block Kit Builder (https://app.slack.com/block-kit-builder) to design and preview message layouts.
- Use
mrkdwnfor inline formatting:*bold*,_italic_,`code`, - Mention users with
<@USER_ID>, channels with<#CHANNEL_ID>, and groups with<!subteam^GROUP_ID>. - Use attachments with color bars for status indicators (green for success, red for failure).
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.
- 1mo ago First seen · 52 lines · 10 tokens per session scan A b53256f42e0f
slack-tools is a skill published in the GitHub repository ginkida/rustyhand (20 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 608 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to slack-tools, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
triggers
Set up, list, or manage triggers — persistent "do Y when X happens" rules. Use when someone asks Archie to do something on a schedule ("every weekday at 9am…", "every morning post…", "remind the channel weekly…"), to react to new messages in a channel ("whenever someone posts X in.
thread-conduct
Use before posting outside this task's thread or deciding how much to post inside it. Covers escalation, cross-channel mandates, thread volume and requests to stop, step aside or go away. Triggers on "escalate this", "let the owners know", "flag this to #channel", "post this in", "who should I tell", "should I update…
hive.browser-automation
Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…
hive.worker-delegation
Concrete patterns for breaking colony work into parallel worker jobs via runplaybook — when fan-out helps, how to model the goal as a tracker table, write the worker skill, author the playbook, pilot, and let convergence retry/resume the gap.
hive.linkedin-automation
Read before automating LinkedIn with browser tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Types CSP that silently drops innerHTML, Lexical composer, native beforeunload dialogs that hang the bridge, and aggressive spam filters — each has bitten us at least once. Verified flows for profile…
hive.x-automation
Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…