slack-agent-mesh: Instructions file for Codex

AGENTS.md

slack-agent-mesh AGENTS.md is an instructions file for Codex, OpenCode from nickvasilescu/slack-agent-mesh. It costs 994 tokens per session, scanned A, original, MIT.

A set of instructions for Slack Agent Mesh, a coordination layer that gives existing AI agents Slack identities and routes messages between them. It explains the project, setup options, demos, tests, and rules for agent authors.

In plain words
What is it for?
Use it to onboard contributors, run the credential-free demo, connect an agent, and follow the project’s development rules.
Why use it?
It helps an agent or operator understand how messages are admitted, delegated, and routed without confusing the coordination layer with the agents’ actual reasoning.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: reads ~/.codex or $CODEX_HOME, but also the file is AGENTS.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is nickvasilescu/slack-agent-mesh's own configuration. It tells Codex and OpenCode how to work on slack-agent-mesh itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything slack-agent-mesh configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/nickvasilescu/slack-agent-mesh/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/nickvasilescu/slack-agent-mesh

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for slack-agent-mesh AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nickvasilescu/slack-agent-mesh/agents-md.svg)](https://agentmods.dev/instructions/nickvasilescu/slack-agent-mesh/agents-md)
Your own site
<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>
Per session 994 This file is loaded in full into every session.
When invoked 994 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 6d ago against content hash 3da7f6a47356, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

AGENTS.md · 84 lines

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)

  1. 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; only env_allowlist + env_pass names are forwarded. This is how you wire Hermes, Claude Code, Codex, or any CLI.
  2. Remote HTTP (webhook adapter). The mesh POSTs signed JSON (x-mesh-signature: v0=… HMAC-SHA256) and expects { "text": "…" } back.
  3. MCP client (MCP server). MCP-capable agents call mesh_send, mesh_reply, mesh_read_thread, mesh_list_agents, mesh_get_trace, mesh_set_presence, and mesh_add_reaction over stdio.

Per-agent, copy-paste onboarding lives in skills/slack-agent-mesh/:

Read the full file on GitHub · 84 lines

Changes

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.

  1. 6d ago First seen · 84 lines · 994 tokens per session scan A 3da7f6a47356

Subscribe to this mod's changes

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.

Related

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens