Borrowing it
Nothing to install: this file belongs to yukukotani/monoread. 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/yukukotani/monoread/main/CLAUDE.mdgit clone --depth 1 https://github.com/yukukotani/monoreadWrote 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/yukukotani/monoread/claude-md)<a href="https://agentmods.dev/instructions/yukukotani/monoread/claude-md"><img src="https://agentmods.dev/badge/instructions/yukukotani/monoread/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.00505 | $0.00505 |
| Opus 5 | $0.00253 | $0.00253 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
monoread 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 8d 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 — 55 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.
Project Overview
monoread is a CLI tool and MCP server for reading web page content in AI-optimized format. It provides high-quality content extraction using Mozilla Readability and llms.txt standards.
Development Commands
pnpm dev: Run in development modepnpm build: Build for productionpnpm test/pnpm test:watch/pnpm test:coverage: Run testspnpm lint: Run all linting (Biome + TypeScript)pnpm fix: Fix linting issues automaticallypnpm mcp/pnpm mcp:debug: Run as MCP server
Architecture
Layered Architecture
- Presentation Layer (
src/presentation/): CLI (gunshi) and MCP server - Use Case Layer (
src/usecase/): Business logic and content providers - Libs (
src/libs/): Domain-independent utilities
Content Provider System
Multi-provider fallback system: GithubProvider → ReadabilityProvider → LlmsTxtProvider → HttpProvider. Each implements ContentProvider interface with canHandle() and extractContent() methods.
Development Rules
Core Principles
- Language: TypeScript with strict type checking
- Paradigm: Functional programming (functions over classes)
- Error Handling: Tagged unions instead of throwing errors
- Conversation: You MUST respond in Japanese
- Comments: You MUST NOT keep descriptions of changes in code
Testing (TDD)
- Follow t-wada's Test-Driven Development
- Create failing tests first, then make them pass
- Test files in same directory as source files (
.test.tsextension) - Tech: vitest, power-assert-monorepo
Commit Workflow
- Small, frequent commits per task
- Run
pnpm lintbefore each commit - Write commit messages in Japanese
- Mark todos completed immediately after committing
Directory Structure
You MUST follow this structure and ask user before adding new directories under src/:
src/presentation/: CLI and MCP server implementationssrc/usecase/: Business logic and providerssrc/libs/: Domain-independent utilities
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.
- 8d ago First seen · 55 lines · 505 tokens per session scan A f0cf8d3bfc97
monoread CLAUDE.md is an instructions file published in the GitHub repository yukukotani/monoread (11 stars, last pushed 11mo ago), licensed Apache-2.0. It adds 505 tokens to every session, about $0.0025 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
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.