Borrowing it
Nothing to install: this file belongs to nickvasilescu/slack-agent-mesh. 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/nickvasilescu/slack-agent-mesh/main/AGENTS.mdgit clone --depth 1 https://github.com/nickvasilescu/slack-agent-meshWrote 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/nickvasilescu/slack-agent-mesh/agents-md)<a href="https://agentmods.dev/instructions/nickvasilescu/slack-agent-mesh/agents-md"><img src="https://agentmods.dev/badge/instructions/nickvasilescu/slack-agent-mesh/agents-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.00994 | $0.00994 |
| Opus 5 | $0.00497 | $0.00497 |
| Sonnet 5 | $0.00199 | $0.00199 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
slack-agent-mesh AGENTS.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 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — onboarding for agents and their operators
This file is the fast path for connecting an agent to Slack Agent Mesh, or for an
AI coding agent working in this repository. It is user-facing onboarding, not the
build specification — the build spec lives in CLAUDE.md and docs/ACCEPTANCE.md.
What this repo is (30 seconds)
Slack Agent Mesh is a transport and coordination layer, not a brain. It gives
your existing agents Slack identities (@rook, @scout), admits only messages
that are actually directed at the mesh, invokes your agents through adapters, and
routes agent-to-agent delegation while preventing loops. Your agent stays the
brain; the mesh carries prompts in and replies out.
Read README.md for the full picture. Read docs/ACCEPTANCE.md for the
invariants that must always hold.
Run it without any credentials
npm ci
npm run demo -- --script examples/demo-conversation.json # deterministic human → @rook → @scout
npm test && npm run test:acceptance # 146 tests
The demo and tests use the mock adapter and an in-memory gateway — no Slack app, no tokens, no network.
Connect your agent (three ways)
- Local CLI (command adapter). Any program that reads a prompt on stdin
and writes its reply to stdout. Turn context arrives as
MESH_AGENT,MESH_TRACE_ID,MESH_HOP,MESH_CHANNEL,MESH_THREAD_TS,MESH_FROM. The child starts from an empty environment; onlyenv_allowlist+env_passnames are forwarded. This is how you wire Hermes, Claude Code, Codex, or any CLI. - Remote HTTP (webhook adapter). The mesh POSTs signed JSON
(
x-mesh-signature: v0=…HMAC-SHA256) and expects{ "text": "…" }back. - MCP client (MCP server). MCP-capable agents call
mesh_send,mesh_reply,mesh_read_thread,mesh_list_agents,mesh_get_trace,mesh_set_presence, andmesh_add_reactionover stdio.
Per-agent, copy-paste onboarding lives in
skills/slack-agent-mesh/:
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 · 84 lines · 994 tokens per session scan A 3da7f6a47356
slack-agent-mesh AGENTS.md is an instructions file published in the GitHub repository nickvasilescu/slack-agent-mesh (1 stars, last pushed 1mo ago), licensed MIT. It adds 994 tokens to every session, about $0.0050 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).
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).
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.