Borrowing it
Nothing to install: this file belongs to KacemMathlouthi/benday. 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/KacemMathlouthi/benday/main/CLAUDE.mdgit clone --depth 1 https://github.com/KacemMathlouthi/bendayWrote 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/kacemmathlouthi/benday/claude-md)<a href="https://agentmods.dev/instructions/kacemmathlouthi/benday/claude-md"><img src="https://agentmods.dev/badge/instructions/kacemmathlouthi/benday/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.01409 | $0.01409 |
| Opus 5 | $0.00705 | $0.00705 |
| Sonnet 5 | $0.00282 | $0.00282 |
| Haiku 4.5 | $0.00141 | $0.00141 |
Grade A, and why
benday 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 — 65 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.
CONTRIBUTING.md is the human-facing guide and is accurate — read it for the contribution workflow, the changeset rules, and the test rationale. This file covers what is only visible after reading across several files.
Commands
Bun workspaces driven by turbo. Run everything from the repo root.
bun install
bun run dev # registry:build, then the docs site on :5173
bun run check # lint and format (ultracite / oxlint + oxfmt)
bun run fix # apply what check reports
bun run typecheck
bun run test # the registry suite
bun run knip # unused files, exports, dependencies
bun run build # registry payloads, then every app
bun run registry:build # regenerate apps/web/public/r/*.json only
CI runs check, typecheck, test, knip, registry:build, a git diff --exit-code on apps/web/public/r, and build.
A single test file or a single test — bun test has no turbo wrapper worth using here:
cd registry && bun test tests/bake.test.ts
cd registry && bun test -t "normalizes depth"
The one structural rule
registry/ is the product. It mirrors the tree the shadcn CLI writes into a consumer's project, which is why its internal imports are relative (./benday/renderer) and never aliased, and why only React may be imported. apps/web reaches the same source through the @registry/* alias instead of keeping a copy, so every example on the docs site is the code that ships.
apps/web/public/r/*.json is generated by registry:build and committed. Any change under registry/ must be committed together with the regenerated payloads and a changeset, or CI fails on drift.
Architecture
The pipeline is image → DotMap → canvas. bake.ts rasterizes a logo, separates ink from background (alpha when the source has soft pixels, otherwise a luminance mask estimated from the corners), derives a separate tone channel, runs an exact Euclidean distance transform so every dot carries its depth inside the shape, and grid-samples the result. The output is small and JSON-serializable on purpose: consumers can run the bake at build time and pass dotMap instead of src, skipping all of it on the client. bake is browser-only — it goes through a canvas.
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 · 65 lines · 1,409 tokens per session scan A 352057c1efe6
benday CLAUDE.md is an instructions file published in the GitHub repository KacemMathlouthi/benday (27 stars, last pushed 8d ago), licensed MIT. It adds 1,409 tokens to every session, about $0.0070 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.