Borrowing it
Nothing to install: this file belongs to bitqs/Slime. 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/bitqs/Slime/master/AGENTS.mdgit clone --depth 1 https://github.com/bitqs/SlimeWrote 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/bitqs/slime/agents-md)<a href="https://agentmods.dev/instructions/bitqs/slime/agents-md"><img src="https://agentmods.dev/badge/instructions/bitqs/slime/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/bitqs/slime/agents-md"><img src="https://agentmods.dev/badge/instructions/bitqs/slime/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.02038 | $0.02038 |
| Opus 5.5 | $0.00815 | $0.00815 |
| Sonnet 5.5 | $0.00408 | $0.00408 |
| Haiku 4.5 | $0.00204 | $0.00204 |
Grade A, and why
Slime 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 1mo 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — read this first, then you can ship
The single onboarding doc for any coding agent or vibe-coder working on Slime.
Read it top to bottom and you can collaborate without breaking anything. It is
harness-neutral; CLAUDE.md is the Claude-Code-specific companion, and
docs/STRUCTURE.md is the full file-by-file map.
What Slime is
A zero-dependency, zero-build plugin that renders a real coding session as a turn-based RPG. Hooks observe every prompt and tool call and append battle events to an append-only stream; three read-only consumers visualize them — a statusline HUD, a tmux pane, and a PixiJS browser arena. Your work goals are the bosses; your plugins are your gear.
The prime directive (never violate)
Observer principle. The plugin must never change the real session. With Slime installed, the agent's behavior must be byte-identical to without it. Therefore:
- Hooks are fail-soft: whole body in
try/catch, alwaysprocess.exit(0), never block, no LLM calls in the hot path (the heuristiccore/estimate.jsexists precisely to avoid one). - Consumers (
statusline.js,watch.js,serve.js) are read-only w.r.t. game state. The sole exception:serve.jswrites thelangpreference toconfig.jsonon an explicit user click (POST /set-lang, 127.0.0.1-only, validated) — a UI preference, not game state, and it never touches Claude's session, so the observer principle still holds. Nothing else underSLIME_ROOTis written by a consumer.
The other hard rules
- Zero runtime deps, zero build. No npm install to run; no bundler; no
.tssource. TypeScript is dev-only via JSDoc +tsc --checkJs. The browser arena vendorspublic/vendor/pixi.min.js— never a CDN.devDependenciesare fine. - Statusline safety. Anything rendered to the terminal goes through
hud.sanitize(strips control chars / ANSI — state files are untrusted input replayed every keystroke). Arena DOM usestextContent/escHtml, neverinnerHTML. - Flash safety. Arena flashes are capped ≤3/sec by the sequencer governor;
?calm=1andprefers-reduced-motionmust keep degrading new effects. - Determinism / replay-stability. State is replayed from the event stream and
polled every keystroke. Do not use
Math.random()in render or hook hot paths — derive "randomness" from an event index/hash (seemapper'shash) so output is stable across replays. Money/XP/unlocks are persisted once, never re-derived. - i18n. User-facing strings live in
data/locales/{en,zh}.json(flat key→string;locale.tfalls back to en). Add both languages for every new key. Player resource is Token (boss HP keeps "HP"). - Test isolation. Every test sets
process.env.SLIME_ROOTto a tmpdir before requiring libs (ROOT is captured at require time) and cleans up after.
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.
- 1mo ago First seen · 141 lines · 2,038 tokens per session scan A 14d679a6ae58
Slime AGENTS.md is an instructions file published in the GitHub repository bitqs/Slime (1 stars, last pushed 4d ago), licensed MIT. It adds 2,038 tokens to every session, about $0.0082 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).