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/s-soroosh/claude-code-js/claude-mdgit clone --depth 1 https://github.com/s-soroosh/claude-code-jsWrote 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/s-soroosh/claude-code-js/claude-md)<a href="https://agentmods.dev/instructions/s-soroosh/claude-code-js/claude-md"><img src="https://agentmods.dev/badge/instructions/s-soroosh/claude-code-js/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 | $0.00601 | $0.00601 |
| Opus 5 | $0.00300 | $0.00300 |
| Sonnet 5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
claude-code-js 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 5d 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 — 66 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.
Common Development Commands
Build and Development
npm run build- Build the TypeScript project to dist/npm run dev- Watch mode for development (rebuilds on file changes)npm run clean- Remove the dist/ directory
Testing
npm test- Run all tests using Vitestnpm test -- tests/claude-code.test.ts- Run a specific test filenpm test -- --coverage- Run tests with coverage report
Code Quality
npm run lint- Run ESLint on all TypeScript filesnpm run typecheck- Run TypeScript type checking without emitting filesnpm run format- Format code using Prettier
Publishing
npm run prepublishOnly- Automatically runs clean and build before publishing
Architecture Overview
This is a TypeScript SDK wrapper for the claude-code CLI. The architecture follows a clean separation of concerns:
Core Components
-
ClaudeCode Class (
src/claude-code.ts): Main entry point that wraps the claude CLI- Handles command construction with proper JSON output format
- Manages API key, model, and working directory options
- Provides methods:
chat(),newSession(),version() - Uses execa for process execution
-
Session Class (
src/session.ts): Manages multi-turn conversations- Tracks session IDs and message history
- Maintains conversation context across multiple prompts
- Automatically resumes the last session ID when continuing conversations
-
Command Utilities (
src/commands.ts): Low-level process executionexecuteCommand()- Executes commands and returns full outputstreamCommand()- Provides real-time streaming of command output- Both use execa under the hood for robust process management
-
Type Definitions (
src/types.ts): TypeScript interfaces for type safety- Defines all request/response shapes
- Provides proper typing for options, messages, and errors
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.
- 5d ago First seen · 66 lines · 601 tokens per session scan A 9425ac623bf1
claude-code-js CLAUDE.md is an instructions file published in the GitHub repository s-soroosh/claude-code-js (55 stars, last pushed 1y ago), licensed MIT. It adds 601 tokens to every session, about $0.0030 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
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).
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.
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 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-release stance: foundation over blast radius, repository layout, commands and host sandbox failures.