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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/homenshum/nodebenchai/agents-md"><img src="https://agentmods.dev/badge/instructions/homenshum/nodebenchai/agents-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/agents-md"><img src="https://agentmods.dev/badge/instructions/homenshum/nodebenchai/agents-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.30304 | $0.30304 |
| Opus 5.5 | $0.12122 | $0.12122 |
| Sonnet 5.5 | $0.06061 | $0.06061 |
| Haiku 4.5 | $0.03030 | $0.03030 |
Grade C, and why
NodeBenchAI AGENTS.md scanned grade C with 3 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
requests.post("https://nodebench-mcp-unified.onrender.com", Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Claude Code** (`~/.claude/settings.json`): Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Health: `curl https://nodebench-mcp-unified.onrender.com/health` (must return `{"status":"ok","tools":114}`) How it starts
The opening of the file, as written. The whole thing — 2,466 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NodeBench Agent Workflow
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 (Codex ↔ Claude) — read FIRST
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): scan
Active claims, claim your region before you start, and hand off new backend
contracts there. Never convex deploy/deploy:prod out-of-band to the shared prod
deployment — it pushes un-reviewed schema/functions and breaks the other agent's next
deploy (this caused a Convex schema-validation incident this session). Declare new
shared-table fields v.optional(...) and announce them in the ledger instead.
Prod-parity and UI kit workflow
Use this rule before any UI, design-system, route-parity, or newly uploaded UI kit task.
Source of truth:
- Git source of truth:
origin/main - Start UI/design work from a clean worktree based on
origin/main. - In this desktop session, the clean prod-parity worktree is
D:\VSCode Projects\cafecorner_nodebench\nodebench_ai4\nodebench-ai\.worktrees\prod-parity-runtime. - A UI kit packet is a design target, not an implementation branch.
Rules:
- Do not work from
hotfix/workspace-routing-exportunless the user explicitly names one file to salvage. - Do not wholesale merge old dirty worktrees or old design/parity branches.
- Start from prod parity, inspect the new UI kit packet, compare, then implement only the delta.
- Preserve live Convex-backed runtime flows; no silent fixture fallback in production paths.
- Preserve web nav as
Home - Reports - Chat - Inbox - Me. - Keep Workspace as a separate deployed surface, not a sixth web tab.
- Verify against the latest UI kit packet and current prod/prod-parity screenshots, not stale local branch screenshots.
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 c9c7d6c66597
- 1mo ago First seen · 2,459 lines · 30,200 tokens per session scan C aedd6a398ba9
NodeBenchAI AGENTS.md is an instructions file published in the GitHub repository HomenShum/NodeBenchAI (15 stars, last pushed 3d ago), licensed MIT. It adds 30,304 tokens to every session, about $0.1212 per session on Opus 5.5. A static security scan graded it C with 3 findings (sends data to an external url, reads agent configuration directories, makes network calls). 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.