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/ryanrawlingswang/llm-rules/claude-mdgit clone --depth 1 https://github.com/ryanrawlingswang/llm-rulesWrote 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/ryanrawlingswang/llm-rules/claude-md)<a href="https://agentmods.dev/instructions/ryanrawlingswang/llm-rules/claude-md"><img src="https://agentmods.dev/badge/instructions/ryanrawlingswang/llm-rules/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.01810 | $0.01810 |
| Opus 5 | $0.00905 | $0.00905 |
| Sonnet 5 | $0.00362 | $0.00362 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
llm-rules 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 4d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Instructions
Stack
- Monorepo: pnpm workspaces + Turborepo
- Web app: Next.js 15 (App Router), TypeScript strict, Tailwind CSS v4
- Auth: Better Auth (email/password, session cookies)
- API: tRPC v11 with
publicProcedure/protectedProcedure - DB: PostgreSQL + Drizzle ORM (
packages/db) - Testing: Vitest + Testing Library + Playwright (e2e)
- Logging:
packages/logger(structured logging — prefer overconsole.log) - i18n:
packages/i18n(translations vianext-intl)
Architecture Principles
Server-first rendering
- Pages are Server Components by default. Only add
"use client"to leaf components that need interactivity — browser APIs, event handlers, or hooks. - Do server-side data fetching in RSC via
getSession(), tRPC server caller, or server actions. Pass results down as props — do not re-fetch on the client what was already fetched on the server. - Protect pages at the RSC level (
getSession()→ redirect) and in middleware. Both layers.
Small, composable components
- One component = one responsibility. If a component has more than ~150 lines, it's doing too much.
- Prefer pure presentational components that receive props over components that fetch their own data.
- Compose complex UIs from small primitives (
Button,Input,Card) rather than building monolithic page components. - Co-locate page-specific components in
_components/next to their route. Shared components go insrc/components/. - Follow DRY: extract reusable logic, components, and utilities. On the backend, share via tRPC procedures or shared libraries. On the frontend, share via hooks, components, and utility functions.
Separation of concerns
src/
app/ ← routing, layouts, pages (thin — orchestrate, don't compute)
_components/ ← page-scoped components (not shared)
components/ui/ ← design system primitives (stateless, no data fetching)
server/api/ ← tRPC routers (application logic, auth, validation — call services)
server/services/ ← service layer (pure business logic, DB access)
lib/ ← shared utilities, auth config, constants
db/ ← DB client + re-exports from packages/db
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.
- 4d ago First seen · 149 lines · 1,810 tokens per session scan A a6cb6700a60c
llm-rules CLAUDE.md is an instructions file published in the GitHub repository ryanrawlingswang/llm-rules (17 stars, last pushed 2mo ago), licensed MIT. It adds 1,810 tokens to every session, about $0.0090 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.