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 agentmods add skills/sliamh11/deus/add-slacknpx skills add sliamh11/Deus --skill add-slackgit clone --depth 1 https://github.com/sliamh11/DeusWrote 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/sliamh11/deus/add-slack)<a href="https://agentmods.dev/skills/sliamh11/deus/add-slack"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/add-slack.svg" alt="Measured on agentmods" 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.00029 | $0.01709 |
| Opus 5 | $0.00015 | $0.00855 |
| Sonnet 5 | $0.00006 | $0.00342 |
| Haiku 4.5 | $0.00003 | $0.00171 |
Grade A, and why
add-slack scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Via API: `curl -s -H "Authorization: Bearer $SLACK_BOT_TOKEN" "https://slack.com/api/conversations.list" | jq '.channels[] | {id, name}'` How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Slack Channel
Status: Coming soon — this channel will be available as
@deus-ai/slack-mcp. The MCP package is not yet available.
This skill will add Slack support to Deus once the MCP package is released. In the meantime, the setup/config/registration phases below describe what the integration will look like.
Phase 1: Setup (Future)
Create Slack App (if needed)
If the user doesn't have a Slack app, share SLACK_SETUP.md which has step-by-step instructions with screenshots guidance, troubleshooting, and a token reference table.
Quick summary of what's needed:
- Create a Slack app at api.slack.com/apps
- Enable Socket Mode and generate an App-Level Token (
xapp-...) - Subscribe to bot events:
message.channels,message.groups,message.im - Add OAuth scopes:
chat:write,channels:history,groups:history,im:history,channels:read,groups:read,users:read - Install to workspace and copy the Bot Token (
xoxb-...)
Configure environment
Add to .env:
SLACK_BOT_TOKEN=xoxb-your-bot-token
SLACK_APP_TOKEN=xapp-your-app-token
Channels auto-enable when their credentials are present — no extra configuration needed.
Sync to container environment:
mkdir -p data/env && cp .env data/env/env
The container reads environment from data/env/env, not .env directly.
Phase 2: Registration (Future)
Get Channel ID
Tell the user:
- Add the bot to a Slack channel (right-click channel → View channel details → Integrations → Add apps)
- In that channel, the channel ID is in the URL when you open it in a browser:
https://app.slack.com/client/T.../C0123456789— theC...part is the channel ID- Alternatively, right-click the channel name → Copy link — the channel ID is the last path segment
The JID format for Deus is:
slack:C0123456789
Register the channel
The channel ID, name, and folder name are needed. Use npx tsx setup/index.ts --step register with the appropriate flags.
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 · 150 lines · 29 tokens per session scan A 118adb9ef102
add-slack is a skill published in the GitHub repository sliamh11/Deus (51 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 1,709 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
memcord
Privacy-first, self-hosted chat memory for OpenClaw — save and recall conversation history across sessions without any cloud dependency.
roadmap-build
Build or repair a roadmap that agents can actually execute, not just read. Produces a single validated YAML source of truth, generated views, definitions of done with evidence kinds, a task pool linked on two axes, an idea intake queue, and three standing checks that keep it honest. Use when asked to "build a…
Research for Datacore
Automated research — source processing, podcast generation, and knowledge extraction.
GTD for Datacore
Getting Things Done — task capture, inbox processing, and org-mode management.
Outbox for Datacore
Content routing — archive to server, search archived content.
research-status
Check research queue counts, recent podcasts, knowledge base growth, and Readwise items.