blog: Instructions file for Claude Code

CLAUDE.md

blog CLAUDE.md is an instructions file for Claude Code from jaxx2104/blog. It costs 1,951 tokens per session, scanned C, original, MIT.

Project instructions for a blog built with Vite, TanStack Start, and pnpm, including development, building, deployment, image handling, and text checks.

In plain words
What is it for?
Use them when developing the blog, checking Japanese writing, optimizing images, building for deployment, or handling cached link-preview data.
Why use it?
They give the coding agent the repository's commands and rules so changes can be tested and built in the expected way.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is jaxx2104/blog's own configuration. It tells Claude Code how to work on blog itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything blog configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jaxx2104/blog. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jaxx2104/blog/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/jaxx2104/blog

Made for: Claude Code.

Wrote 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.

agentmods badge for blog CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jaxx2104/blog/claude-md.svg)](https://agentmods.dev/instructions/jaxx2104/blog/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/jaxx2104/blog/claude-md"><img src="https://agentmods.dev/badge/instructions/jaxx2104/blog/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,951 This file is loaded in full into every session.
When invoked 1,951 The same file — it is already loaded in full.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01951 $0.01951
Opus 5 $0.00975 $0.00975
Sonnet 5 $0.00390 $0.00390
Haiku 4.5 $0.00195 $0.00195

Measured 7d ago against content hash 1136a66fa61d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade C, and why

blog CLAUDE.md scanned grade C with 2 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

`rm -rf <output-dir> && pnpm test` before pushing.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

`curl -s localhost:PORT/ | grep -ao 'style-[^"]*\.css'` has to match
CLAUDE.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 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

Development

pnpm dev         # Start Vite dev server (TanStack Start)
pnpm build       # Run velite build + vite build (prerender to dist/client/)
pnpm start       # Serve dist/ via vite preview
pnpm deploy      # Alias for pnpm build
pnpm optimize:images  # Re-encode content/posts images (pass --dry-run first)

pnpm build reaches the network to fill data/ogp-cache.json for any link card URL it has not seen, and to re-check entries older than 90 days. Set OGP_OFFLINE=1 to render fallback cards instead, or OGP_OFFLINE=strict to fail the build on a cache miss. CI builds with strict, so a post that adds a link needs the cache entry your local build produced to be committed with it. A URL that will never resolve goes in data/ogp-unfetchable.json instead.

Code Quality

pnpm lint                # Run Biome with --write
pnpm lint:ci             # Run Biome ci (no fixes; fails on warnings/errors)
pnpm lint:text           # Check Japanese text in blog posts (textlint)
pnpm lint:textfix        # Auto-fix Japanese text issues
pnpm test                # Run unit tests (vitest run)
pnpm test:types          # Run TypeScript type checking (tsc -p)
pnpm format              # Format code with Biome

Stack

A statically prerendered blog: TanStack Start (Vite + React) over a Velite + Zod content layer, CSS Modules, Biome, Vitest, pnpm, deployed to Cloudflare Pages. package.json is the source of truth for versions; what is worth knowing beyond it:

  • Vite 8 bundles with rolldown, not rollup. Chunking behaves differently — see the pitfalls below before touching chunk configuration
  • CSS ships as one asset (build.cssCodeSplit: false). Code-split CSS drops the previous route's stylesheet during SPA navigation, leaving the navi and footer unstyled until a hard reload
  • Velite writes two things: .velite/ for the build to read, and public/content/ for the client to fetch. Syntax highlighting (shiki + rehype-pretty-code) happens there, so it never reaches the browser
  • Specs live next to their source as *.test.ts / *.test.tsx

Read the full file on GitHub · 140 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. 7d ago First seen · 140 lines · 1,951 tokens per session scan C 1136a66fa61d

Subscribe to this mod's changes

blog CLAUDE.md is an instructions file published in the GitHub repository jaxx2104/blog (5 stars, last pushed 5d ago), licensed MIT. It adds 1,951 tokens to every session, about $0.0098 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens