Borrowing it
Nothing to install: this file belongs to HomenShum/NodeBenchAI. 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/HomenShum/NodeBenchAI/main/CLAUDE.mdgit clone --depth 1 https://github.com/HomenShum/NodeBenchAIWrote 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/homenshum/nodebenchai/claude-md)<a href="https://agentmods.dev/instructions/homenshum/nodebenchai/claude-md"><img src="https://agentmods.dev/badge/instructions/homenshum/nodebenchai/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/homenshum/nodebenchai/claude-md"><img src="https://agentmods.dev/badge/instructions/homenshum/nodebenchai/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.04733 | $0.04733 |
| Opus 5.5 | $0.01893 | $0.01893 |
| Sonnet 5.5 | $0.00947 | $0.00947 |
| Haiku 4.5 | $0.00473 | $0.00473 |
Grade A, and why
NodeBenchAI 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 18d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NodeBench AI — Claude Code Project Instructions
New to this repository? Read docs/START_HERE.md first. It follows one
question from the keypress to the answer, step by step through the real files,
and tells you what you can run without a Convex deployment. Everything below
assumes you already know that path. Its line citations and the CodeTour steps
in .tours/ are checked by node scripts/validate-tours.mjs — run that after
moving any code those documents point at.
Agent coordination (read FIRST when other agents may be active)
AGENT_COORDINATION.md (repo root) is the live ledger of who is editing what right now
and what backend contracts are ready to call. Before editing a hot file
(public/proto/home-v5.html, backend/convex/events.ts, backend/convex/schema/eventsSchema.ts, the
ScratchNode e2e specs): scan its Active claims, claim your region before you start,
hand off new backend contracts there, and never convex deploy/deploy:prod
out-of-band to shared prod (declare new shared-table fields v.optional and announce them
instead). This prevents the cross-agent collisions — schema drift, file-churn — that caused
a real prod incident during the ScratchNode session.
Deploy & merge workflow (P0 — read before merging anything)
The repo's branch protection now enforces:
- Required CI checks on every PR:
CI / Typecheck,CI / Runtime smoke,CI / Build enforce_admins: true— admin merges DO NOT bypass these checks anymore
Use gh pr merge <N> --auto --squash --delete-branch, NOT --admin --squash.
--autowaits for required checks then auto-merges. Same speed as--adminfor green PRs.--adminwill be rejected by the platform on any PR that hasn't passed CI.- If you legitimately need to merge a CI-failing PR (rare), the user must lower the gate manually.
Vercel deploy webhook: the GitHub→Vercel push integration silently dropped events earlier (project link's sourceless: true flag). It was re-wired via vercel git disconnect && vercel git connect. As belt-and-suspenders, .github/workflows/vercel-deploy-hook-backup.yml curls a Deploy Hook URL on every push to main. Required repo secret: VERCEL_DEPLOY_HOOK_URL (already set). If this drift recurs, run gh secret list to confirm the secret is still there + check the workflow's last run for non-2xx.
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.
- 18d ago Changed · +7 lines · +104 tokens per session 15c5f744ffa1
- 1mo ago First seen · 201 lines · 4,629 tokens per session scan A d1320372d536
NodeBenchAI CLAUDE.md is an instructions file published in the GitHub repository HomenShum/NodeBenchAI (15 stars, last pushed 3d ago), licensed MIT. It adds 4,733 tokens to every session, about $0.0189 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.