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/shofer-dev/claude-code-slang-orchestrator/agents-mdgit clone --depth 1 https://github.com/shofer-dev/claude-code-slang-orchestratorWrote 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/shofer-dev/claude-code-slang-orchestrator/agents-md)<a href="https://agentmods.dev/instructions/shofer-dev/claude-code-slang-orchestrator/agents-md"><img src="https://agentmods.dev/badge/instructions/shofer-dev/claude-code-slang-orchestrator/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 | $0.01184 | $0.01184 |
| Opus 5 | $0.00592 | $0.00592 |
| Sonnet 5 | $0.00237 | $0.00237 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
claude-code-slang-orchestrator 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 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent working agreements — slang-orchestrator
Durable rules for changing this plugin. Current-state only. Full detail lives in
DESIGN.md (rationale + invariants) and slang_specs.md (the language). This
file is the short version; don't duplicate those docs here.
What this is
A Claude Code plugin: a stdio MCP server (server/) hosting a deterministic,
non-LLM executor that runs typed .slang multi-agent workflows. Each agent is
a Claude Agent SDK session; the executor coordinates them (contracts,
tool-scoping, termination). The top-level session only triggers/observes.
Stack & conventions
- TypeScript ESM, Node ≥20 (server
engines; README/benchmark ask Node 22+), pnpm. All source is underserver/; run every command from there. tsconfig:strict,target ES2022,moduleResolution: Bundler,noEmit. Indent with tabs (matches existing.ts;.mjshooks use 2 spaces).- Relative imports use
.jsextensions on.tssources (bundler/ESM). - No ESLint/Prettier config in the repo — match surrounding style by hand.
@modelcontextprotocol/sdkandzodare version-pinned; keep them pinned.@anthropic-ai/claude-agent-sdkis only needed for real runs — the whole test suite mocks it, so tests need no SDK, noclaudeCLI, no API key, no network.
Build / test / run (all in server/)
pnpm typecheck—tsc --noEmitover the server.pnpm test—node --test --import tsx test/*.test.ts(unit + conformance; no model calls).pnpm dev/start— run the stdio MCP server (tsx src/main.ts; logs to stderr, stdout is the MCP channel).pnpm build— esbuild bundle todist/main.js(nottscemit) and copiessrc/*.mjs→dist/.- Root shortcut
pnpm check= typecheck + test. A husky pre-push hook runs both and blocks the push (active only when this folder is its own git repo). Leave the tree green before committing a module you touched.
Non-obvious invariants (read before changing 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.
- 4d ago First seen · 76 lines · 1,184 tokens per session scan A 4ec44471d17a
claude-code-slang-orchestrator AGENTS.md is an instructions file published in the GitHub repository shofer-dev/claude-code-slang-orchestrator (1 stars, last pushed 5d ago), licensed Apache-2.0. It adds 1,184 tokens to every session, about $0.0059 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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.