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/stevenn/ctxlayer/claude-mdgit clone --depth 1 https://github.com/stevenn/ctxlayerWhat 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.05018 | $0.05018 |
| Opus 5 | $0.02509 | $0.02509 |
| Sonnet 5 | $0.01004 | $0.01004 |
| Haiku 4.5 | $0.00502 | $0.00502 |
Grade A, and why
ctxlayer CLAUDE.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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ctxlayer — Claude Code Briefing
This repo is the agent context layer: a remote MCP server on Cloudflare that serves curated docs (with RAG over Vectorize), proxies upstream MCP servers with centralised per-user credentials, and exposes a React SPA for self onboarding + collaborative markdown editing + admin/usage analytics.
docs/PLAN.md is the architecture & data-model reference — not a roadmap. The
milestone-driven plan that built ctxlayer (M1–M8) is retired; future work proceeds
ad hoc, tracked in code + commits + this file, not in a larger plan. Topic deep-dives
are under docs/plan/ (A: auth, B: stdio bridge, C: upstream proxy, D: UI+REST,
E: dev environment, F: org IA, G: conventions, I: upstream resilience, M: OKF
interop, N: OKF bundles). Skim
PLAN.md for the lay of the land and pull in a deep-dive when the topic comes up —
but trust the code first; these docs are reference, not kept in lockstep with every change.
What runs where
- Cloudflare Worker (
apps/worker/) is the single deployable unit. It hosts: the MCP server (/mcp,/sse), the OAuth provider (/oauth/*,/.well-known/oauth-authorization-server), REST endpoints for the SPA (/api/*), IdP callbacks (/idp/*), the realtime collab endpoint (/collab/:id), and the React SPA via Workers Assets. - React SPA (
apps/web/) is built with Vite and shipped fromapps/web/distby the Worker. - Shared types (
packages/shared/) — Zod schemas + types used by both Worker and SPA.
Architecture pointers
- MCP per-session state → Durable Object
McpSessionDO(apps/worker/src/mcp/session-do.ts). - Per-doc realtime collab → Durable Object
DocRoomDO(apps/worker/src/collab/doc-room-do.ts). - HTTP/SSE upstreams are proxied directly through the generic
UpstreamClientinterface (apps/worker/src/upstream/*.ts). Stdio MCP servers are not run by ctxlayer: the operator fronts them with their own stdio↔HTTP bridge (e.g.supergateway) and registers the resulting HTTP URL as an ordinarystreamable_httpupstream (bring-your-own-bridge). - All sensitive material is sealed with AES-GCM via
crypto/aead.ts.
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 · 331 lines · 5,018 tokens per session scan A 1a25f69ee02d
ctxlayer CLAUDE.md is an instructions file published in the GitHub repository stevenn/ctxlayer (9 stars, last pushed 4d ago), licensed MIT. It adds 5,018 tokens to every session, about $0.0251 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
projektor AGENTS.md
Instructions for TAJD/projektor, covering agents.md, what projektor is, coordination model (read this first), planning and design docs live in the wiki, not the repo and architecture: the service-layer contract (most important).
projektor CLAUDE.md
Instructions for TAJD/projektor: See AGENTS.md for guidance on working in this codebase.
capacities-mcp-worker CLAUDE.md
Claude Code instructions for tieubao/capacities-mcp-worker, covering claude.md, what this is, commands, architecture and key dependencies.
vibesdk AGENTS.md
AGENTS.md instructions for cloudflare/vibesdk, covering agents.md, tooling, verification, frontend ui and frontend data fetching.
munkel CLAUDE.md
Instructions for limehq/munkel, covering claude.md, monorepo layout, commands, macos development specifics and deploy.
cloudbox AGENTS.md
Instructions for acoyfellow/cloudbox, covering cloudbox agent guide, canonical commands, deploy model, cloudflare account boundaries and required production secrets.