Borrowing it
Nothing to install: this file belongs to RamaAditya49/titen. 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/RamaAditya49/titen/main/CLAUDE.mdgit clone --depth 1 https://github.com/RamaAditya49/titenWrote 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/ramaaditya49/titen/claude-md)<a href="https://agentmods.dev/instructions/ramaaditya49/titen/claude-md"><img src="https://agentmods.dev/badge/instructions/ramaaditya49/titen/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.00747 | $0.00747 |
| Opus 5 | $0.00374 | $0.00374 |
| Sonnet 5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
titen 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 7d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code (claude.ai/code) in this repository.
Read AGENTS.md first
AGENTS.md is the authoritative agent contract: product framing,
reading order, the spec -> plan -> implement -> done lifecycle, coding
constraints, the simplicity budget, security, and verification rules. It is not
duplicated here. This file only adds what an agent cannot infer from it.
Commands
| Task | Command |
|---|---|
| Install | pnpm install |
| Memory service (local) | pnpm titen serve — Bun + SQLite on 127.0.0.1:8787 |
| Bootstrap org + owner key | pnpm titen bootstrap --org 'My Org' |
| Contract + SDK tests | pnpm test:api (Bun) |
| Integration tests | pnpm test:integration |
| Dashboard build + browser tests | pnpm test |
| Everything | pnpm test:all |
| Workflow doc check (before handoff) | pnpm check:workflow |
| Cloudflare dry-run build | pnpm build:worker |
A single test file: bun test tests/contract/<name>.test.ts.
Two runtimes, one core
src/core/** has zero external imports and uses Web Standards only. That is
load-bearing, not incidental — it is what lets the same kernel run on
bun:sqlite and on Cloudflare D1 against one contract suite. Keep it that way:
- Runtime-specific code goes in
src/runtime/bun/**orsrc/runtime/cloudflare/**. bun:sqliteappears in exactly one file,src/runtime/bun/sqlite.ts.sqlite-vecis loaded through a lazyrequire()insrc/runtime/bun/vectors.tsand is anoptionalDependency; retrieval degrades to lexical FTS5 when it is absent, and/readyzreports the capability as disabled.
Publishing to npm
Releases are manual, from a maintainer's machine — never a GitHub Action.
The full procedure is docs/engineering/release.md.
Two facts that will bite an agent editing package.json:
filesis an allowlist that overrides.gitignore, which is the only reason the gitignoreddist/npm/sdk.jsreaches the tarball. Adding a build output outsidefilessilently ships nothing.astro,wrangler,playwright, andminiflareare devDependencies on purpose. Promoting any of them todependenciesinstalls a build toolchain on every consumer's disk.
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.
- 7d ago First seen · 65 lines · 747 tokens per session scan A 94b3bf976a6f
titen CLAUDE.md is an instructions file published in the GitHub repository RamaAditya49/titen (12 stars, last pushed 8d ago), licensed Apache-2.0. It adds 747 tokens to every session, about $0.0037 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-30.
Other instructions, from other repositories
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).
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.
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).
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.