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 commands/tdimino/claude-code-minoan/slack-syncgit clone --depth 1 https://github.com/tdimino/claude-code-minoanWrote 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/commands/tdimino/claude-code-minoan/slack-sync)<a href="https://agentmods.dev/commands/tdimino/claude-code-minoan/slack-sync"><img src="https://agentmods.dev/badge/commands/tdimino/claude-code-minoan/slack-sync.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.00000 | $0.00696 |
| Opus 5 | $0.00000 | $0.00348 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
slack-sync 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 6d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack Sync
Bind this session to a Slack channel. After binding, the session registry shows this session as connected to the channel, and Claudicle can post status updates there.
Arguments
Target: $ARGUMENTS
If empty, show the current binding status and active sessions.
Instructions
If no arguments: Show Status
python3 ~/.claude/hooks/soul-registry.py list --md
Print the output and stop.
If a channel is specified:
Step 1: Resolve the Channel
If the argument starts with C and looks like a Slack channel ID (e.g., C12345), use it directly. Otherwise, treat it as a channel name (strip leading # if present) and resolve it:
source ~/.zshrc 2>/dev/null; python3 ~/.claude/skills/slack/scripts/slack_channels.py --filter "CHANNEL_NAME" --json
Parse the JSON output to find the matching channel ID and name.
Step 2: Ensure Listener Is Running
python3 ~/.claude/skills/slack/daemon/slack_listen.py --status
If not running, start it:
cd ~/.claude/skills/slack/daemon && python3 slack_listen.py --bg
Step 3: Bind in Registry
The session ID is available from the environment or hook context. Use it to bind:
python3 ~/.claude/hooks/soul-registry.py bind "SESSION_ID" "CHANNEL_ID" "#CHANNEL_NAME"
Replace SESSION_ID with the current session's UUID.
Step 4: Post Announcement
source ~/.zshrc 2>/dev/null; python3 ~/.claude/skills/slack/scripts/slack_post.py "CHANNEL_ID" "_Claudicle connected from $(basename $(pwd))_"
Step 5: Confirm
Print:
Session bound to #channel-name. This session is now visible in the soul registry as connected to that channel.
Important
- The session must already be registered (happens automatically via the SessionStart hook).
- Binding is per-session. When the session ends, the registry entry is cleaned up.
- Multiple sessions can bind to the same channel.
- To unbind, just exit the session or start a new one without
/slack-sync.
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.
- 6d ago First seen · 88 lines · 0 tokens per session scan A 234a18d9dc85
slack-sync is a command published in the GitHub repository tdimino/claude-code-minoan (41 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 696 tokens. 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 commands, from other repositories
ui-evidence
Discover, configure, and run ui-evidence for before/after UI review in this repo.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
fec-smell
Diagnose frontend code smells with evidence and candidate refactorings without changing business code.
spec-forge
Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.
bmad-edit-prd
DEPRECATED — consolidated into bmad-prd update intent - this skill will be removed in v7 in favor of bmad-prd.
operational-playbook-creator
Create comprehensive operational playbook documenting organizational structure, processes, meeting rhythms, communication protocols, OKRs, tools, onboarding, and culture. Build the operating system that scales your team from 10 to 1,000+ employees.