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/terry-cyx/newton-cli/claude-mdgit clone --depth 1 https://github.com/Terry-cyx/newton-cliWrote 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/terry-cyx/newton-cli/claude-md)<a href="https://agentmods.dev/instructions/terry-cyx/newton-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/terry-cyx/newton-cli/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.01859 | $0.01859 |
| Opus 5 | $0.00929 | $0.00929 |
| Sonnet 5 | $0.00372 | $0.00372 |
| Haiku 4.5 | $0.00186 | $0.00186 |
Grade A, and why
newton-cli 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 — 111 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.
Project goal
Build newton-cli — an agent-native CLI wrapper around NVIDIA's Newton physics engine — so an LLM agent can drive Newton without writing Python.
Defining principle: Newton's examples/ directory is the spec. The CLI is "complete" when every example under ../newton/newton/examples/ can be reproduced by a sequence of newton-cli invocations that pass the example's own test_final() validation. We do not enumerate Newton's API surface top-down; we grow the CLI bottom-up from real example demand. If a CLI command isn't needed to run an example, it doesn't get built (yet).
Repository layout (standard src layout)
This project lives at E:/newton-cli/newton_cli/. The vendored Newton source is a sibling at E:/newton-cli/newton/. The two-folder split keeps upstream untouched.
E:/newton-cli/
├── newton/ # vendored upstream Newton (read-only)
└── newton_cli/ # THIS project
├── .venv/ # local virtualenv (uv)
├── pyproject.toml # depends on newton via path "../newton"
├── README.md
├── CLAUDE.md # this file
├── PLAN.md # wave-by-wave execution plan
├── src/
│ └── newton_cli/ # the Python package
│ ├── __init__.py
│ ├── __main__.py # lazy-inits Warp under stdout redirect
│ ├── cli.py # argparse dispatcher
│ ├── io.py # emit / fail envelope helpers
│ ├── _introspect.py # allow-list API walker
│ ├── _warp.py # silent Warp init
│ ├── recipes.py # JSON recipe → ModelBuilder
│ ├── sim.py # step loop
│ └── state_io.py # .npz round-trip
├── tests/
│ ├── _cli.py # subprocess runner helper
│ ├── test_phase0_introspection.py
│ └── test_examples/ # one test file per Newton example
├── logs/ # wave logs + session summaries
└── prompts/ # prompt fragments (bootstrap etc.)
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 · 111 lines · 1,859 tokens per session scan A 6e2115ec6a4c
newton-cli CLAUDE.md is an instructions file published in the GitHub repository Terry-cyx/newton-cli (5 stars, last pushed 4mo ago), licensed MIT. It adds 1,859 tokens to every session, about $0.0093 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-31.
Other instructions, from other repositories
claudemon CLAUDE.md
Instructions for zamarrowski/claudemon, covering ai agent guidelines, project shape, general guidelines, general rules and guards & defensive code.
unity-code-style-guide AGENTS.md
Instructions for krogh-jacobsen/unity-code-style-guide, covering agents.md — unity 6 c, project setup — edit this block, never do these — they corrupt the project, deprecated in unity 6 and if you read nothing else.
nes-php-glfw copilot-instructions.md
Instructions for oliverearl/nes-php-glfw, covering github copilot development guidelines for nes emulator, agent document source of truth, project overview, code style & standards and documentation.
game-and-watch-retro-go-sd CLAUDE.md
Claude Code instructions for sylverb/game-and-watch-retro-go-sd, covering claude.md, what this project is, build / flash workflow, architecture and three storage tiers, one elf.
base-building-trap-defense-design-agent-skill CLAUDE.md
Instructions for dungnotnull/base-building-trap-defense-design-agent-skill, covering claude.md — skill 250: base-building-trap-defense-design, skill identity, problem this skill solves, harness flow summary and sub-skills.
trident-mcp AGENTS.md
Instructions for mordor-forge/trident-mcp, covering agents.md, what this is, build and test, single-file verification and e2e tests.