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/ykdojo/safeclaw/slacknpx skills add ykdojo/safeclaw --skill slackgit clone --depth 1 https://github.com/ykdojo/safeclawWrote 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/ykdojo/safeclaw/slack)<a href="https://agentmods.dev/skills/ykdojo/safeclaw/slack"><img src="https://agentmods.dev/badge/skills/ykdojo/safeclaw/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 | $0.00023 | $0.00217 |
| Opus 5 | $0.00012 | $0.00109 |
| Sonnet 5 | $0.00005 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- slack — 100% identical, 0 lines differ
What it actually says
Slack Read Tool
Use ~/tools/slack-read.js to read Slack data:
# List channels
node ~/tools/slack-read.js channels
# List DMs
node ~/tools/slack-read.js dms
# Read channel history (last 20 messages)
node ~/tools/slack-read.js history <channel_id>
node ~/tools/slack-read.js history <channel_id> 50 # last 50
# Search messages
node ~/tools/slack-read.js search "keyword"
node ~/tools/slack-read.js search "from:@user in:#channel"
# List users
node ~/tools/slack-read.js users
# Get channel info
node ~/tools/slack-read.js info <channel_id>
- This is read-only - you cannot send messages or modify anything
- Requires SLACK_TOKEN env var (run
./scripts/setup-slack.shon host)
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.
- 4d ago First seen · 34 lines · 23 tokens per session scan A e7c9dccfa0af
slack is a skill published in the GitHub repository ykdojo/safeclaw (181 stars, last pushed 6d ago), licensed MIT. It adds 23 tokens to every session and 217 once invoked, about $0.0001 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
swift-study
Interactive Swift/iOS tutor with two modes. Classic explains first, Mastery uses a predict-first Core Loop with gates.
study-summary
Saves learning notes from the current conversation. Classic mode makes concise notes, Mastery mode keeps detailed training artifacts.
swift-quiz
Adaptive Swift/iOS quiz with two modes. Classic is lighter, Mastery requires mechanism-level reasoning.
start
Use this skill when the user runs /start, says "start", "enable the SDLC workflow", "I want to build", "I want to fix", "set up", "get started", or otherwise signals they want to activate or re-enable the SDLC workflow. Handles three distinct paths based on marker state — fresh install (opt-in activation), re-enable…
plan
Use this skill at the START of every coding task — new builds, bug fixes, and change requests. Classifies the work item, validates it against project scope, produces a high-level estimate, proposes a technology stack, and checks stack compatibility. Writes a plan artifact to .claude/sdlc/plans/ that every downstream…
configure
Use this skill when the user runs /configure, /configure --needs, or /configure --check. Also auto-invoked by env-detect.sh on fresh install (Layer 0) and by skills that find required config missing at runtime (Layer 2). Guides setup of config/tools.json and config/tools.local.json through a question bank; handles…