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/homenshum/nodebenchai/claude-mdgit clone --depth 1 https://github.com/HomenShum/NodeBenchAIWhat 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.04629 | $0.04629 |
| Opus 5 | $0.02315 | $0.02315 |
| Sonnet 5 | $0.00926 | $0.00926 |
| Haiku 4.5 | $0.00463 | $0.00463 |
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 2d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NodeBench AI — Claude Code Project Instructions
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.
If a deploy is stuck: prefer vercel build --prod && vercel deploy --prebuilt --prod over vercel --prod (latter uploads CWD's Windows-locked package-lock and breaks on sharp linux-x64). vercel redeploy <url> rebuilds the SAME commit, not current main — useless for getting recent merges live.
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.
- 2d 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 (14 stars, last pushed 19d ago), licensed MIT. It adds 4,629 tokens to every session, about $0.0231 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
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
agentgateway copilot-instructions.md
Copilot instructions for agentgateway/agentgateway: Do not check for, speculate about, or report compilation errors during code review. Compilation diagnostics from review are frequently incorrect; rely on CI to detect and report compilation failures.
hatch3r CLAUDE.md
Instructions for hatch3r/hatch3r, covering hatch3r — development instructions, architecture, development commands, two-axis pillar framework (2.0.0) and orchestrator self-discipline (bypass protection).
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
ken CLAUDE.md
Instructions for townsendmerino/ken, covering claude.md, what this is, repository ownership (read this first), commands and embedding parity & golden fixtures (now in aikit).
gangsta GEMINI.md
Instructions for kucherenko/gangsta, a project described as: AI agentic skills framework for spec-driven development, built on the organizational model of mafia.