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/logosdx/monorepo/claude-mdgit clone --depth 1 https://github.com/logosdx/monorepoWrote 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/logosdx/monorepo/claude-md)<a href="https://agentmods.dev/instructions/logosdx/monorepo/claude-md"><img src="https://agentmods.dev/badge/instructions/logosdx/monorepo/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 | $0.03007 | $0.03007 |
| Opus 5 | $0.01503 | $0.01503 |
| Sonnet 5 | $0.00601 | $0.00601 |
| Haiku 4.5 | $0.00301 | $0.00301 |
Grade A, and why
monorepo 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 5d 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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
🚀 Commands
# Build/Test
pnpm build
pnpm test
pnpm tdd # Watch mode
pnpm test:only # Run marked tests (it.only)
pnpm test:coverage
# Workflow
pnpm new # Create package
pnpm watch # Dev mode
pnpm build:docs
pnpm release # Changesets
# Individual tests (from tests/)
pnpm test filepart # Run test whose filename contains "filepart"
pnpm tdd # Watch specific tests
📦 Release Cycle
We use Changesets, publishing straight from master.
Publishing is triggered by a package version change on master — merging the
"Version Packages" PR is the signal. No separate release branch.
Quick Reference
```bash
# 1. Create changeset for your changes
pnpm changeset
# 2. Commit and push to master
git add . && git commit -m "feat: description" && git push
# 3. CI creates "Version Packages" PR - review and merge to master
# 4. Merging the PR bumps versions on master, which triggers CI to
# automatically: Publish → Update docs
```
Detailed Flow
- Create Changeset:
pnpm changeset- describes changes and version bump - Push to Master: CI runs tests and creates "Version Packages" PR
- Review PR: Verify versions and changelogs are correct
- Merge PR: version bump on
mastertriggers the publish workflow - Automated CI: publishes to npm, updates documentation
See CONTRIBUTING.md for complete release documentation.
🏗️ Architecture
Structure: pnpm monorepo, packages build independently, test together
Repository Structure Overview
monorepo/
├── packages/ # 9 @logosdx packages in layered architecture
│ ├── utils/ # Foundation layer (all packages depend on this)
│ ├── dom/ # Browser utilities (depends on utils)
│ ├── fetch/ # HTTP client (depends on utils)
│ ├── observer/ # Event system (depends on utils)
│ ├── localize/ # i18n system (depends on utils)
│ ├── state-machine/ # State management (depends on utils)
│ ├── storage/ # Persistence layer (depends on utils)
│ └── react/ # React bindings (optional peer deps on above)
│
├── tests/ # Comprehensive test suite
│ ├── src/ # Test files mirroring package structure
│ ├── benchmark/ # Performance tests (250k ops, memory monitoring)
│ └── package.json # Test dependencies (vitest, sinon, jsdom, fast-check)
│
├── docs/ # VitePress documentation + TypeDoc integration
│ ├── packages/ # Individual package documentation
│ ├── public/images/ # Brand assets and static files
│ └── *.md # Getting started, philosophy, cheat sheets
│
├── skills/logosdx/ # Claude Code skill with package reference guides
│ ├── SKILL.md # Skill definition and routing
│ └── references/ # Per-package API reference files
├── scripts/ # Build, documentation, and workflow scripts
├── internals/ # Internal utilities and templates
├── typedoc/ # Generated API documentation
└── CLAUDE.md # This file - development guidance
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.
- 5d ago First seen · 367 lines · 3,007 tokens per session scan A bd4e649b68bc
monorepo CLAUDE.md is an instructions file published in the GitHub repository logosdx/monorepo (7 stars, last pushed 20d ago), licensed BSD-3-Clause. It adds 3,007 tokens to every session, about $0.0150 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).
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.
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).