Borrowing it
Nothing to install: this file belongs to OutlitAI/outlit-sdk. 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/OutlitAI/outlit-sdk/main/CLAUDE.mdgit clone --depth 1 https://github.com/OutlitAI/outlit-sdkWrote 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/outlitai/outlit-sdk/claude-md)<a href="https://agentmods.dev/instructions/outlitai/outlit-sdk/claude-md"><img src="https://agentmods.dev/badge/instructions/outlitai/outlit-sdk/claude-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.1 | $0.00873 | $0.00873 |
| Opus 5 | $0.00436 | $0.00436 |
| Sonnet 5 | $0.00175 | $0.00175 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
outlit-sdk 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 today.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Outlit SDK
Read AGENTS.md for shared repository workflow and task scope before applying the guidance below.
Monorepo for Outlit's TypeScript tracking SDKs (@outlit/core, @outlit/browser, @outlit/node) and CLI (@outlit/cli).
Tech stack
- Runtime: Bun (v1.3.9, set via
packageManagerin rootpackage.json) - Build: Turbo + tsup
- Linting/formatting: Biome
- Testing: Vitest (unit), Playwright (browser e2e)
- Releases: Changesets (
@changesets/cli) — stable releases and canary snapshots via GitHub Actions - Rust crate (
crates/outlit): released separately viarelease-plz
Project structure
packages/
core/ # Shared types and utilities (dependency of browser + node)
browser/ # Browser SDK with React and Vue bindings
node/ # Node.js server-side SDK
cli/ # CLI tool (Rust binary published via npm)
typescript-config/ # Shared tsconfig
Common commands
bun install # Install deps
bun run build # Build all packages (turbo)
bun run test # Run all tests
bun run typecheck # Type-check all packages
bun run lint # Lint with biome
bun run changeset # Create a changeset for your changes
Publishing rules
Never use workspace:* (or any workspace: protocol) in dependencies of published packages. Use concrete version ranges (e.g. "^1.1.0") instead. devDependencies may use workspace:* since they are excluded from published tarballs.
Why: Changesets uses npm publish under the hood (even in bun workspaces). npm publish does not resolve the workspace: protocol, so it leaks verbatim into the published tarball and breaks consumers — especially those using bun workspaces.
Bun workspaces resolve any matching version range to the local package, so concrete ranges like "^1.1.0" work identically to workspace:* during local development. Changesets' updateInternalDependencies: "patch" setting keeps these ranges in sync when dependency versions are bumped.
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.
- today Changed · +2 lines · +40 tokens per session cc84da3d1ce8
- 7d ago First seen · 69 lines · 833 tokens per session scan A 44b385b5762f
outlit-sdk CLAUDE.md is an instructions file published in the GitHub repository OutlitAI/outlit-sdk (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 873 tokens to every session, about $0.0044 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
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.
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.
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).
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).
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.
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.