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.
git clone --depth 1 https://github.com/sttts/slagentWrote 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/plugins/sttts/slagent/slaude)<a href="https://agentmods.dev/plugins/sttts/slagent/slaude"><img src="https://agentmods.dev/badge/plugins/sttts/slagent/slaude/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/plugins/sttts/slagent/slaude"><img src="https://agentmods.dev/badge/plugins/sttts/slagent/slaude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sttts-slaude 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.
What it actually says
{
"name": "sttts-slaude",
"description": "Start, stop, join, resume, and manage Claude Code sessions mirrored to Slack via slaude",
"version": "v2026.3.27-alpha.1",
"author": {
"name": "Stefan Schimanski",
"url": "https://github.com/sttts"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 0 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 10 lines scan A 4fb70a5053e9
sttts-slaude is a plugin published in the GitHub repository sttts/slagent (22 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
slack
Slack AI tools for users and developers: interact with your workspace via the Slack MCP server and use skills to develop Slack apps.
slackcli
Drive Slack from Claude Code with the slackcli binary: installs it if missing, checks authentication, then reads, sends, searches, and manages a workspace.
full-process
Drives a full feature-development workflow (clarify -> design -> plan -> execute -> PR -> test) over Slack via the claude-slack-bridge daemon. Ships /process-setup for one-time per-repo configuration and /process for clarification + handoff to the daemon's workflow engine.
scv
SCV (Standard · Cowork · Verify) — Claude Code plugin for team workflows. Every change becomes a plan + tests before merging, and those tests accumulate into a self-running regression suite. Built-in Slack/Discord reporting and supersedes-based test obsolescence. Run /scv:help to start.
slack-workspace
The entire Slack Web API for Claude Code — 201 methods, approval-gated sending, a cached workspace reference, and scheduled-job alerting. Backed by the elnora-slack CLI.
standup-ghost
Never write a standup again. Composes and posts your daily standup from what you actually did — Jira, GitHub, Claude Code sessions, Google Calendar — on a schedule, unattended.