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 instructions/jamessmoore/slack-mcp/claude-mdgit clone --depth 1 https://github.com/jamessmoore/slack-mcpWrote 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/jamessmoore/slack-mcp/claude-md)<a href="https://agentmods.dev/instructions/jamessmoore/slack-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/jamessmoore/slack-mcp/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.02384 | $0.02384 |
| Opus 5 | $0.01192 | $0.01192 |
| Sonnet 5 | $0.00477 | $0.00477 |
| Haiku 4.5 | $0.00238 | $0.00238 |
Grade A, and why
slack-mcp 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 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code when working in this repository.
Project
An AWS-native MCP server exposing post_to_slack/post_file_to_slack,
reachable via an Amazon Bedrock AgentCore Gateway (AWS_IAM authorizer) so
AWS-internal AI callers can post to Slack mid-reasoning without each project
vendoring its own copy of the Slack integration. Backend is a Lambda
(container image, Python 3.13) running a FastMCP streamable-HTTP server
wrapped for Lambda via Mangum, fronted directly by an API Gateway HTTP API
(AWS_PROXY integration — no VPC Link/ALB/ECS hop). See README.md for
the full architecture diagram and rationale.
This is a re-hosting of tool logic that already exists and is already
proven in the sibling repo daily-tech-brief-bedrock
(app/slack_mcp_server/index.js, a vendored Node.js MCP server called over
stdio) — server/slack_tools.py is a faithful Python port of that logic,
not a rewrite, kept wire-compatible (same tool names, same chunking
constant) so migrating callers is a drop-in swap. The AgentCore
Gateway/Lambda/API Gateway pattern itself is copied from CoreSample,
which deployed and verified the identical shape end-to-end in production
before being torn down (see CoreSample/CLAUDE.md).
Deliberately scoped to one AI caller for now (daily-tech-brief-bedrock),
not a shared multi-project server. A separate project, webtechhq-site,
also posts to Slack but via a raw incoming webhook with no LLM in the
trigger path — that's a packaged automation, not a tool-use decision, so it
has no reason to go through MCP and is explicitly out of scope here (see
the vault's PROJECTS/slack-mcp.md 2026-07-15 scope decision).
Current status — read before assuming anything is stale
As of this writing: live and deployed. Real AWS resources exist and the
full CI/CD path (feature branch → PR → passing test CI → merge to main
→ auto-triggered .github/workflows/deploy.yml via GitHub OIDC →
terraform apply → image build/push → aws lambda update-function-code)
has been proven end-to-end more than once. Current shape:
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 · 190 lines · 2,384 tokens per session scan A ce1dc208be5c
slack-mcp CLAUDE.md is an instructions file published in the GitHub repository jamessmoore/slack-mcp (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,384 tokens to every session, about $0.0119 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-31.
Other instructions, from other repositories
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).
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.
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.
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.
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).