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/leavittsoftware/titanium-elements/claude-mdgit clone --depth 1 https://github.com/LeavittSoftware/titanium-elementsWhat 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.01446 | $0.01446 |
| Opus 5 | $0.00723 | $0.00723 |
| Sonnet 5 | $0.00289 | $0.00289 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
titanium-elements 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project Overview
titanium-elements is a monorepo that publishes @leavittsoftware/web — Lit 3 + Material Web custom elements used across Leavitt Group front-end applications.
titanium-*— general-purpose UI components (drawers, data tables, inputs, snackbars, etc.)leavitt-*— domain-specific components (company/person selects, file explorer, app shell, API helpers); many require authentication and anApiServiceinstance
The package is published to npm and consumed via deep imports (no barrel index.ts exports).
Tech Stack
- Framework: Lit 3 — web components with Shadow DOM
- UI base: Material Web (
@material/web/*) - Language: TypeScript (strict, decorators enabled)
- Shared types:
@leavittsoftware/lg-core-typescriptfor OData entity interfaces - Monorepo: npm workspaces + Lerna (independent versioning)
- Component docs: Custom Elements Manifest →
packages/leavittbook/custom-elements.json - Peer dependency:
lit >= 3.0.0
Monorepo Structure
packages/
web/ # @leavittsoftware/web — all published elements (titanium/ + leavitt/)
leavittbook/ # Local component gallery and demos (not published); see packages/leavittbook/CLAUDE.md
Within packages/web:
titanium/ # General-purpose components, helpers, styles, events
leavitt/ # Domain components, app shell, api-service, auth
Key Scripts
npm start # tsc watch + web-dev-server + CEM watch
npm run build # tsc + tests + CEM + leavittbook rollup
npm run lint # prettier + eslint + lit-analyzer + tsc
npm run lint-fix # auto-fix formatting and lint issues
npm run cem # regenerate custom-elements-manifest
npm run lerna:publish # build + conventional publish to npm
Run npm run lint after edits and fix issues in changed files before committing.
Development Workflow
npm ithennpm start— browse component demos in leavittbook- New component: copy an existing folder under
packages/web, add a leavittbook demo + route, add a tsconfig path - Conventional Commits required (
feat:,fix:,chore:, etc.) - CEM output at
packages/leavittbook/custom-elements.jsonhelps verify APIs but is not shipped with@leavittsoftware/web
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 · 118 lines · 1,446 tokens per session scan A 785cb621a699
titanium-elements CLAUDE.md is an instructions file published in the GitHub repository LeavittSoftware/titanium-elements (20 stars, last pushed 4d ago), licensed MIT. It adds 1,446 tokens to every session, about $0.0072 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
bce.design AGENTS.md
Instructions for AdamBien/bce.design, covering agents.md, project overview, template usage, development commands and running the application.
maui copilot-instructions.md
Guidance for GitHub Copilot when working on the .NET MAUI repository.
maui uitests.instructions.md
Instructions for dotnet/maui, covering ui testing guidelines for .net maui, ui test structure, two-project requirement, base class and infrastructure and naming conventions.
maui helix-device-tests.instructions.md
Guidelines for running and configuring .NET MAUI device tests on Helix infrastructure.
maui ci-copilot-pipeline-security.instructions.md
Security rules for the Copilot PR-review pipeline. Read before editing.
maui xaml-unittests.instructions.md
Guidelines for writing XAML unit tests in the Controls.Xaml.UnitTests project.