Borrowing it
Nothing to install: this file belongs to MH4GF/rulens. 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/MH4GF/rulens/main/CLAUDE.mdgit clone --depth 1 https://github.com/MH4GF/rulensWrote 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/mh4gf/rulens/claude-md)<a href="https://agentmods.dev/instructions/mh4gf/rulens/claude-md"><img src="https://agentmods.dev/badge/instructions/mh4gf/rulens/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.01564 | $0.01564 |
| Opus 5 | $0.00782 | $0.00782 |
| Sonnet 5 | $0.00313 | $0.00313 |
| Haiku 4.5 | $0.00156 | $0.00156 |
Grade A, and why
rulens 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 — 122 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
Rulens is a CLI tool for extracting, documenting, and formatting linting rules from various linting tools (currently supporting Biome and ESLint). It generates comprehensive Markdown documentation to help developers understand and follow the project's coding standards.
Documentation
IMPORTANT: Always read all documentation in the docs/ directory at the start of each session. This includes:
docs/lint-rules.md- Explains linting rules and coding standardsdocs/requirements.md- Project requirements and technical specificationsdocs/todos.md- Task tracking for project implementation (CRITICAL to understand and update)- Any additional files in the
docs/directory
Pay special attention to docs/todos.md as it provides a clear roadmap of implemented features and pending tasks. Always update this file when implementing new features to reflect progress accurately.
Commands
- Build:
pnpm build- Build the project using tsup - Dev:
pnpm dev- Watch mode for development - Format:
pnpm fmt- Run all formatters (syncpack, biome) - Lint:
pnpm lint- Run all linters (biome, tsc, syncpack) - Run after making changes - Test:
pnpm test- Run all tests - Single test:
pnpm test path/to/test.ts- Run specific test - Test with watch:
pnpm test:watch- Run tests in watch mode - Coverage:
pnpm test:coverage- Run tests with coverage report - Changeset:
pnpm changeset- Create a new changeset (always write in English)
Workflow Commands:
Always run pnpm lint and pnpm test after implementing new features to verify your changes.
Coding Guidelines
- IMPORTANT: Always follow @docs/lint-rules.md as coding guideline
- File Structure: Place tests alongside implementation files (e.g., foo.ts, foo.test.ts)
- Type Safety: Avoid eslint-disable directives and type assertions (as keyword), use valibot for runtime type validation
- External Data: Handle all external data (JSON, API responses) as untrusted and validate with valibot
- Logging: Use the Logger class instead of console.log/error for consistent logging
- Comments: Follow these guidelines for code comments:
- Use JSDoc style comments for functions, classes, and interfaces
- Write comments that explain "why" not "what" the code is doing
- Avoid redundant comments that merely restate the code
- Don't use comments for code organization or section markers; structure your code instead
- Document non-obvious behavior, complex algorithms, or business rules
- Keep comments up-to-date with code changes
- Use English for all comments
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 · 122 lines · 1,564 tokens per session scan A 9155597b8185
rulens CLAUDE.md is an instructions file published in the GitHub repository MH4GF/rulens (11 stars, last pushed 1y ago), licensed MIT. It adds 1,564 tokens to every session, about $0.0078 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.