Borrowing it
Nothing to install: this file belongs to tomeraitz/claude-slack-bridge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tomeraitz/claude-slack-bridge/main/CLAUDE.mdgit clone --depth 1 https://github.com/tomeraitz/claude-slack-bridgeWrote 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/instructions/tomeraitz/claude-slack-bridge/claude-md)<a href="https://agentmods.dev/instructions/tomeraitz/claude-slack-bridge/claude-md"><img src="https://agentmods.dev/badge/instructions/tomeraitz/claude-slack-bridge/claude-md.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.00501 | $0.00501 |
| Opus 5 | $0.00251 | $0.00251 |
| Sonnet 5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
claude-slack-bridge CLAUDE.md 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 8d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Instructions
Communication
Once you use mcp__claude-slack-bridge__ask_on_slack for the first time in a conversation, ALL further communication with the user must go through that tool. Do not use AskUserQuestion, and do not ask questions or request feedback as text in the terminal. Continue communicating exclusively via Slack until the user explicitly tells you to switch back to the terminal.
Exception — setup/configuration skills: The following skills run locally inside Claude Code as part of /process-setup and must use AskUserQuestion (not Slack), even if ask_on_slack was already used earlier in the session:
build-design-workflowbuild-plan-workflowbuild-run-plan-flowbuild-process-skill
While executing any of these skills, follow the skill's own instructions for clarifications (local AskUserQuestion). Resume the Slack-only rule once the skill returns.
Adding a channel → folder route
When asked to route a Slack channel to a project folder, edit projects.json
(repo root) and add one entry:
"#channel-name": "/abs/path/to/project" // simple
"#channel-name": { "path": "/abs/path", "plugin_dir": "/abs/plugin/dir" } // with a plugin dir
Rules:
- The path must be an existing, absolute directory — verify with
ls <path>first. A path that doesn't exist is the #1 cause of "the project directory doesn't exist" replies. If it runs in Docker, the path must exist inside the container (a mounted volume), not just on the host. - The channel key may be
#name, a raw channel ID (C…), or a DM ID (D…). - Don't add comment/placeholder keys (e.g.
"_README") — every key is treated as a channel and an unknown one just logs a warning.
Apply the change without restarting the daemon:
./reload-mapping.sh # prints "reloaded N channel(s)"; warns about any missing dirs
Reloads take effect for new threads immediately; an existing thread whose
directory is unchanged keeps it, and a thread whose directory went missing
re-resolves on its next message. See docs/reloading-projects.md.
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.
- 8d ago First seen · 45 lines · 501 tokens per session scan A 694b9ea7a8ab
claude-slack-bridge CLAUDE.md is an instructions file published in the GitHub repository tomeraitz/claude-slack-bridge (33 stars, last pushed 18d ago), licensed MIT. It adds 501 tokens to every session, about $0.0025 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.