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/sttts/slagent/agents-mdgit clone --depth 1 https://github.com/sttts/slagentWhat 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 | $0.02178 | $0.02178 |
| Opus 5 | $0.01089 | $0.01089 |
| Sonnet 5 | $0.00436 | $0.00436 |
| Haiku 4.5 | $0.00218 | $0.00218 |
Grade A, and why
slagent 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 2d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
slagent — Agent Rules
Project
Go library for streaming agent sessions to Slack threads, plus slaude CLI that wraps Claude Code.
Structure
slagent.go, thread.go, turn.go — Root library: Thread, Turn, NewSlackClient
compat.go, native.go — Compat (postMessage/update) and native (chat.startStream) backends
mrkdwn.go, reply.go — Markdown→mrkdwn, reply polling
credential/ — Load, Save, Extract tokens from Slack desktop app
credential.go — Credentials struct, Load, Save, Path
extract.go, leveldb.go — Extract() orchestrator, LevelDB token reading
cookie.go, decrypt.go, paths.go
channel/ — Resolve, List
channel.go — Client, ResolveByName, ResolveUser, List
cmd/slaude/ — CLI (auth, channels, share, status, start)
main.go
cmd/slaude/internal/
session/session.go — Session orchestration
claude/process.go, events.go — Claude subprocess, stream-JSON parsing
terminal/terminal.go — Terminal UI
perms/server.go, listener.go — MCP permission server for Slack-based tool approval
cmd/slagent-demo/ — Demo CLI
main.go
contrib/ — Project assets
logo.png — Project logo (update here, not root)
Module: github.com/sttts/slagent
Tasks
- Use the task system (TaskCreate/TaskUpdate/TaskList) for everything the user asks.
- Mark tasks in_progress before starting, completed when done.
Commit Rules
- Title convention:
area/subarea: short what has been done - Commit in sensible chunks. Don't mix topics.
- Add files individually (not
git add -A). - Do
git addandgit commitin one command. - Don't push without being asked.
- Before committing, simplify the code. Look deeply at changes.
Build
- ALWAYS build binaries into the repo root after ANY code change:
go build -o slaude ./cmd/slaude/ && go build -o slagent-demo ./cmd/slagent-demo/ && go build -o claude-command-classifier-hook ./cmd/claude-command-classifier-hook/ - Build each binary individually.
go build ./...only checks compilation, it doesn't produce binaries. - The user runs
./slaudefrom the repo root. If you don't rebuild, they test stale code.
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.
- 2d ago First seen · 151 lines · 2,178 tokens per session scan A 3c5dafae5f88
slagent AGENTS.md is an instructions file published in the GitHub repository sttts/slagent (23 stars, last pushed 5mo ago), licensed MIT. It adds 2,178 tokens to every session, about $0.0109 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
chat AGENTS.md
AGENTS.md instructions for vercel/chat, covering agents.md, commands, per-package, monorepo layout and architecture.
agentconnect CLAUDE.md
Instructions for agentconnect-md/agentconnect, covering claude.md, what this is, monorepo (pnpm workspace, packages/), platform modules and comment style.
personal-agent-template AGENTS.md
Instructions for vercel-labs/personal-agent-template, covering personal agent template, quick reference, structure, documentation and eve framework.
macro CLAUDE.md
Claude Code instructions for macro-inc/macro, covering claude.md, architecture overview, key services, data storage and macrodb schema changes.
slack-skills-plugin AGENTS.md
AGENTS.md instructions for slackapi/slack-skills-plugin, covering slack plugin, commands, development commands, cross-skill references and skill descriptions.
Kagura CLAUDE.md
Instructions for Innei/Kagura, covering claude.md, build & run, push & deploy, commit first, then push with lock protection and development workflow.