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/tensorcircuit/tensorcircuit-ng/agents-mdgit clone --depth 1 https://github.com/tensorcircuit/tensorcircuit-ngWhat 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.01291 | $0.01291 |
| Opus 5 | $0.00646 | $0.00646 |
| Sonnet 5 | $0.00258 | $0.00258 |
| Haiku 4.5 | $0.00129 | $0.00129 |
Grade A, and why
tensorcircuit-ng AGENTS.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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TensorCircuit-NG Repository Guide for AI Agents
Mission
TensorCircuit is a tensor-network-first, multi-backend quantum computing framework. Optimize for backend-agnostic, differentiable, JIT-friendly code changes that match existing repository style.
Non-Negotiable Rules
- Use
tc.backendfor core tensor operations. Do not call backend-specific APIs such as NumPy, JAX, or TensorFlow directly in core logic. - Prefer backend-native abstractions already used in the repo, including
tc.backend.jit,tc.backend.grad,tc.backend.vmap, and backend control-flow helpers when applicable. - Preserve differentiability. Avoid graph-breaking conversions, in-place tensor mutation, and other patterns that block autodiff.
- Preserve JIT compatibility. Avoid Python control flow that depends on tensor values; prefer backend control-flow helpers or static structure.
- Keep changes minimal and consistent with existing architecture.
- Prefer simple, direct implementations. Avoid defensive complexity and broad
try...exceptblocks. - Fail fast. Expose real problems early instead of masking them with silent fallbacks or workaround-heavy logic.
- Do not cheat around repository invariants, tests, or framework behavior just to make a local change appear to pass.
- Focus only on git-tracked files. Do not search for or modify files in
.gitignoreunless explicitly specified by the user. tensorcircuit/applicationsandbenchmarks/are deprecated, do not add or modify files there unless the user explicitly specified.
Environment Rules
- Never install packages into system or user Python unless the user explicitly asks.
- If a command fails because of missing Python packages or
ModuleNotFoundError, ask the user which environment to use. - Once the environment is known, run Python tooling through that environment, for example
conda run -n <env> .... - Dependency and tool configuration lives in
requirements/,pyproject.toml, and.pylintrc. - Keep sandbox- or machine-specific execution workarounds out of tracked source files unless the user explicitly asks for a repo-level workaround. Examples include redirecting
MPLCONFIGDIR, cache directories, or other local writable paths just to satisfy the current sandbox. - Do not hardcode or publicly expose local conda environment names, usernames, absolute paths, hostnames, or other machine-specific execution details in tracked docstrings, examples, or user-facing scripts. Use generic placeholders such as
conda run -n <env> ...unless the repository explicitly needs a concrete value.
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 · 72 lines · 1,291 tokens per session scan A c8c249818416
tensorcircuit-ng AGENTS.md is an instructions file published in the GitHub repository tensorcircuit/tensorcircuit-ng (88 stars, last pushed 20d ago), licensed Apache-2.0. It adds 1,291 tokens to every session, about $0.0065 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
PINA AGENTS.md
Instructions for PINA-org/PINA, covering pina — physics-informed neural architectures, quick reference, workflow: problem → model → solver → trainer, problem types and condition types.
tpu_performance_autoresearch_wiki GEMINI.md
Instructions for vlasenkoalexey/tpu_performance_autoresearch_wiki, covering gemini/antigravity operating rules, platform adaptation (claude code → gemini/antigravity), 1. skills — native, no emulation, 2. never-stop hook & retrospectives and 3. session and transcript resolution.
PINA CLAUDE.md
Instructions for PINA-org/PINA, a project described as: Physics-Informed Neural networks for Advanced modeling.
huggingface_hub AGENTS.md
AGENTS.md instructions for huggingface/huggingface_hub, covering agent guide for huggingfacehub, project overview, setup, key commands and code structure.
nnsight CLAUDE.md
Instructions for ndif-team/nnsight, covering nnsight — agent guide, how to use this file, by task, "i want multi-token / autoregressive generation" and "i want to run multiple prompts at once".
elata-bio-sdk AGENTS.md
Instructions for Elata-Biosciences/elata-bio-sdk, covering ai agent guide, what this repo is, first things to read, repo map and canonical commands.