titanium-elements CLAUDE.md

Project-specific instructions for Titanium Elements, a reusable web-component library published to npm. It is organized as a monorepo, meaning several related packages live in one repository.

In plain words
What is it for?
Use them when developing Lit components, working with Material Web, editing the web or demo packages, or managing npm workspaces and Lerna versions.
Why use it?
They explain the package layout, required libraries, documentation format, and release structure so components remain compatible and publishable.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/leavittsoftware/titanium-elements/claude-md
Clone the repo
git clone --depth 1 https://github.com/LeavittSoftware/titanium-elements
Per session 1,446 This file is loaded in full into every session.
When invoked 1,446 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 785cb621a699, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

CLAUDE.md · 118 lines

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 an ApiService instance

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-typescript for 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

  1. npm i then npm start — browse component demos in leavittbook
  2. New component: copy an existing folder under packages/web, add a leavittbook demo + route, add a tsconfig path
  3. Conventional Commits required (feat:, fix:, chore:, etc.)
  4. CEM output at packages/leavittbook/custom-elements.json helps verify APIs but is not shipped with @leavittsoftware/web

Read the full file on GitHub · 118 lines

Changes

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.

  1. 2d ago First seen · 118 lines · 1,446 tokens per session scan A 785cb621a699

Subscribe to this mod's changes

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.