json-difference CLAUDE.md

A guide for working in an Nx workspace, a repository that manages multiple related applications and libraries from one project configuration.

In plain words
What is it for?
It helps explore projects, run builds and tests through Nx, use Nx documentation for unfamiliar options, and follow the correct process for creating project files.
Why use it?
It reduces mistakes caused by running the wrong commands, guessing command options, or ignoring project dependencies.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/lukascivil/json-difference/claude-md
Clone the repo
git clone --depth 1 https://github.com/lukascivil/json-difference
Per session 2,112 This file is loaded in full into every session.
When invoked 2,112 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02112 $0.02112
Opus 5 $0.01056 $0.01056
Sonnet 5 $0.00422 $0.00422
Haiku 4.5 $0.00211 $0.00211

Measured 2d ago against content hash 017ef39df82f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

json-difference 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.

CLAUDE.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 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.

General Guidelines for working with Nx

  • For navigating/exploring the workspace, invoke the nx-workspace skill first - it has patterns for querying projects, targets, and dependencies
  • When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through nx (i.e. nx run, nx run-many, nx affected) instead of using the underlying tooling directly
  • Prefix nx commands with the workspace's package manager (e.g., pnpm nx build, npm exec nx test) - avoids using globally installed CLI
  • You have access to the Nx MCP server and its tools, use them to help the user
  • For Nx plugin best practices, check node_modules/@nx/<plugin>/PLUGIN.md. Not all plugins have this file - proceed without it if unavailable.
  • NEVER guess CLI flags - always check nx_docs or --help first when unsure

Scaffolding & Generators

  • For scaffolding tasks (creating apps, libs, project structure, setup), ALWAYS invoke the nx-generate skill FIRST before exploring or calling MCP tools

When to use nx_docs

  • USE for: advanced config options, unfamiliar flags, migration guides, plugin configuration, edge cases
  • DON'T USE for: basic generator syntax (nx g @nx/react:app), standard commands, things you already know
  • The nx-generate skill handles generator discovery internally - don't call nx_docs just to look up generator syntax

Repository overview

Nx monorepo (yarn 4, berry) that publishes the json-difference library — a path-based JSON delta computer — plus ancillary projects that consume it.

Project Path Type Notes
json-difference libs/json-difference library (published) Core lib, ESM/CJS + standalone browser bundle
json-difference-cli libs/json-difference-cli library (published) jd CLI wrapper (yargs)
mcp-json-diff tools/mcp-json-diff application MCP server exposing the lib via stdio
playground apps/playground application React + Vite demo deployed to GitHub Pages
example apps/example application Runnable Node usage scripts (simple.ts, stress.ts)

Read the full file on GitHub · 116 lines

Changes

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.

  1. 2d ago First seen · 116 lines · 2,112 tokens per session scan A 017ef39df82f

Subscribe to this mod's changes

json-difference CLAUDE.md is an instructions file published in the GitHub repository lukascivil/json-difference (58 stars, last pushed 20d ago), licensed MIT. It adds 2,112 tokens to every session, about $0.0106 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.