Borrowing it
Nothing to install: this file belongs to stevenn/ctxlayer. 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/stevenn/ctxlayer/main/AGENTS.mdgit clone --depth 1 https://github.com/stevenn/ctxlayerWrote 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/stevenn/ctxlayer/agents-md)<a href="https://agentmods.dev/instructions/stevenn/ctxlayer/agents-md"><img src="https://agentmods.dev/badge/instructions/stevenn/ctxlayer/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/stevenn/ctxlayer/agents-md"><img src="https://agentmods.dev/badge/instructions/stevenn/ctxlayer/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.01825 | $0.01825 |
| Opus 5.5 | $0.00730 | $0.00730 |
| Sonnet 5.5 | $0.00365 | $0.00365 |
| Haiku 4.5 | $0.00183 | $0.00183 |
Grade A, and why
ctxlayer 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 2mo 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.
Working in this repo as an agent
Optimised for Claude-on-the-web and mobile sessions. Keep replies terse,
operate via slash commands and bun run scripts, and prefer one-shot
verifies over interactive flows.
Golden path for any change
bun run verify— typecheck + lint (Biome) + unit + integration tests, all offline.bun run verify:fulladditionally runs thesmokesuite, which needs a running local Worker (bun run dev:worker) or a preview URL.- Commit with a present-tense, "why" focused message.
git push -u origin <branch>and open a PR withgh pr create.- There is no hosted CI — run
bun run verifyyourself before pushing.
Where things live
- Cloudflare Worker entry →
apps/worker/src/index.ts - Durable Objects →
apps/worker/src/mcp/session-do.ts,apps/worker/src/collab/doc-room-do.ts - Hono REST routes →
apps/worker/src/api/*.ts - SQL migrations →
apps/worker/src/db/migrations/*.sql - React SPA →
apps/web/src/ - Shared types/schemas →
packages/shared/src/ - OKF (Open Knowledge Format) interop →
packages/shared/src/frontmatter.tsapps/worker/src/docs/okf.ts; the doc rail is the frontmatter editor. Reference →docs/plan/M-okf.md
- Architecture reference →
docs/PLAN.md(reference, not a roadmap)
Module rules
- One file = one concern. Split when a file holds separable concerns — not when it crosses a line count.
- ~300 LoC is a review trigger, not a limit. Past it, ask "is this still one
thing?" A standalone component, a single DO's lifecycle, or one linear
pipeline stays one file however long it runs;
db/queries/docs.ts(three tables + ACL predicates) andmcp/tools-proxy.ts(registry + catalogue read-models + call runner) are the shape that should split. - No circular deps across the four top-level concerns:
api/,mcp/,collab/,queues/. - All env via the typed
Envfromapps/worker/src/env.ts. - All SQL via
apps/worker/src/db/queries/*.ts— never inline in routes.
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.
- 2mo ago First seen · 141 lines · 1,825 tokens per session scan A db0c316a010a
ctxlayer AGENTS.md is an instructions file published in the GitHub repository stevenn/ctxlayer (12 stars, last pushed 17d ago), licensed MIT. It adds 1,825 tokens to every session, about $0.0073 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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.