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 runxhq/runx --skill slackgit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/slack)<a href="https://agentmods.dev/skills/runxhq/runx/slack"><img src="https://agentmods.dev/badge/skills/runxhq/runx/slack.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/runxhq/runx/slack"><img src="https://agentmods.dev/badge/skills/runxhq/runx/slack.svg?style=web" alt="Reviewed on agentmods" width="80" height="15"></a>- NVIDIA SkillSpector pass
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.00032 | $0.01578 |
| Opus 5 | $0.00016 | $0.00789 |
| Sonnet 5 | $0.00006 | $0.00316 |
| Haiku 4.5 | $0.00003 | $0.00158 |
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 5d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack
Use Slack as a governed provider boundary without turning Slack—or Runx Cloud—into the owner of the operator's workflow. This skill owns the reusable Slack mechanics that an agent should not have to reconstruct: bounded message search, bounded thread hydration, digest-bound reply planning, explicit approval, idempotent delivery, and exact-message readback.
The operator-selected provider binding has one narrow role in this flow: retain
credential custody and execute a fixed Slack operation. It may be local,
self-hosted, third-party, or Runx-hosted. The skill, its procedure, approval
point, retry identity, and completion rule remain in Runx OSS. Any queue,
team-specific routing rule, or durable action state belongs in a higher-level
operator skill and normally composes operator-inbox.
Composes
send-as#plan
Runners
search reads one bounded Slack search page. Supply a query object with at
least one of author_external_id, mentions_connected_subject, or keywords.
The exact fields are:
author_external_id: one Slack member id string, such asU123ABCmentions_connected_subject: a boolean selecting messages that mention the member bound to the selected provider accountkeywords: one keyword-mode search phrase string, not an array and not raw Slack search syntaxafterandbefore: ISO-8601 timestamp strings, withafterearlier thanbeforechannel_types: a non-empty array drawn frompublic_channel,private_channel,mpim, andimlimit: an integer from 1 through 20cursor: the opaquenext_cursorfrom the preceding page
The provider rejects embedded Slack modifiers in keywords, enforces the
maximum page, and returns normalized locators and bounded previews rather than
a raw Slack response. Continue only from next_cursor; one page is never proof
that a workspace scan is complete.
read_thread reads one bounded thread page from an exact
slack://workspace/channel/timestamp locator. The limit is capped at 15 because
Slack applies a low limit and, for some non-Marketplace installations, a very
low request cadence to conversations.replies. Hydrate only threads that are
actually needed, preserve next_cursor, and do not fan out speculative reads.
Thread messages include bounded attachment metadata and opaque
slack-file://workspace/file locators; private Slack download URLs never cross
the provider boundary.
What ships with it
5 files 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.
- 5d ago First seen · 138 lines · 32 tokens per session scan A 54c62aceb637
slack is a skill published in the GitHub repository runxhq/runx (84 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 1,578 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-09-03.
Other skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.
dd-sourcing
Document sources properly for due diligence reports. Use when citing any external data, ensuring full traceability and auditability of findings.
dd-verification
Verify claims in pitch decks and founder statements using multiple independent sources. Use when analyzing any claim about market size, traction, team background, or competitive positioning.