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/cyberuni/cyber-slack/agents-mdgit clone --depth 1 https://github.com/cyberuni/cyber-slackWrote 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/cyberuni/cyber-slack/agents-md)<a href="https://agentmods.dev/instructions/cyberuni/cyber-slack/agents-md"><img src="https://agentmods.dev/badge/instructions/cyberuni/cyber-slack/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.00541 | $0.00541 |
| Opus 5 | $0.00270 | $0.00270 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
cyber-slack 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 5d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to AI coding assistants when working with code in this repository.
Project Overview
cyber-slack is a Slack CLI and MCP server for AI agents. It provides:
- CLI: Command-line interface for interacting with Slack
- MCP Server: Model Context Protocol server exposing Slack tools to AI agents
Tech Stack
- Language: TypeScript (strict mode)
- Runtime: Node.js 22+
- Build: tsdown
- Test: Vitest
- Lint/Format: Biome
- Monorepo: pnpm workspaces + Turbo
- Versioning: Changesets
Repository Structure
packages/
cyber-slack/ # Main package: CLI + MCP server
src/
cli.ts # CLI entry point
mcp.ts # MCP server entry point
client.ts # Slack client wrapper
index.ts # Public API exports
Commands
pnpm verify # Full verification: lint + build + typecheck + test + knip
pnpm build # Build all packages
pnpm test # Run tests
pnpm check # Run Biome linting/formatting check
pnpm check:fix # Fix linting/formatting issues
pnpm cs <script> # Run script in packages/cyber-slack
Environment Variables
| Variable | Required | Description |
|---|---|---|
SLACK_BOT_TOKEN |
Yes | Slack Bot User OAuth Token (xoxb-...) |
Code Conventions
- Use TypeScript strict mode
- Prefer functional style
- Use named exports (not default exports)
- Test files:
*.test.tsfor unit tests,*.system.tsfor live API tests - Follow Conventional Commits:
feat:,fix:,refactor:,test:,docs:,chore:
MCP Tools
Tools are registered in src/mcp.ts. Each tool should:
- Check for required environment variables
- Use the Slack client from
client.ts - Return structured responses with
contentarray - Handle errors gracefully with
isError: true
Adding New Tools
- Add the tool registration in
src/mcp.ts - Add tests in
src/*.test.ts - Update the README tool table
- Create a changeset:
pnpm changeset
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.
- 5d ago First seen · 74 lines · 541 tokens per session scan A 517f18213308
cyber-slack AGENTS.md is an instructions file published in the GitHub repository cyberuni/cyber-slack (1 stars, last pushed 19d ago), licensed MIT. It adds 541 tokens to every session, about $0.0027 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
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.
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.
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).