Borrowing it
Nothing to install: this file belongs to savannah-i-g/nanotracker-api-sdk. 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/savannah-i-g/nanotracker-api-sdk/main/AGENTS.mdgit clone --depth 1 https://github.com/savannah-i-g/nanotracker-api-sdkWrote 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/savannah-i-g/nanotracker-api-sdk/agents-md)<a href="https://agentmods.dev/instructions/savannah-i-g/nanotracker-api-sdk/agents-md"><img src="https://agentmods.dev/badge/instructions/savannah-i-g/nanotracker-api-sdk/agents-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.1 | $0.00915 | $0.00915 |
| Opus 5 | $0.00458 | $0.00458 |
| Sonnet 5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
nanotracker-api-sdk 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 8d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nanoTracker API SDK — agent rules
Cross-agent must-know rules for driving a live
nanoTracker session. Per-agent
detail is in CLAUDE.md, .hermes/,
.agents/, and adapters/.
The shape
You call MCP tools or HTTP endpoints on a relay running on
127.0.0.1:9311. The relay forwards to a browser tab where
window.nanoTracker lives. The user must:
- Have started the relay (
node tools/relay.mjs). - Have the nanoTracker tab open.
- Have toggled Enable Local API in FILE > API….
- Have toggled Connect to local relay and pasted the token.
If any of these is false, you get { ok: false, errors: [...] }. Read
the error code, tell the user, do not retry in a loop.
Hard rules
- Every non-dryRun batch needs
opts.undoDescription. patternId≠ order-list index. Resolve viagetPatternList.- Validation is two-phase, all-or-nothing. One bad command rejects the whole batch.
- Use
dryRun: truefor destructive batches against patterns with existing cells. - Prefer
setNoteOffoversetCellwith{ note: 97 }. The dedicated op clears the neighbouring instrument/volume fields so the cell reads as a proper note-off;setCellmerges and leaves them behind. assets.listreturns full relative paths. Samples inside subfolders of<project>/samples/are reachable — pass thenamefield verbatim toassets.load.- Sample binary upload is out of scope. Use
assets.loadto bring files in from<project>/samples/only. - Hard limits: 10,000 commands/batch, 64 patterns created/batch, 1 MiB payload, 20 batches/sec.
Surfaces
read(query)— sync queries. Cheap. No undo.execute(commands, opts)— batched mutations. One undo entry per batch.assets.{list,load,unload}(args)— async, project-only.
Full reference:
docs/PROTOCOL.md,
docs/ASSETS.md.
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.
- 8d ago First seen · 94 lines · 915 tokens per session scan A ee484c88213e
nanotracker-api-sdk AGENTS.md is an instructions file published in the GitHub repository savannah-i-g/nanotracker-api-sdk (20 stars, last pushed 4mo ago), licensed MIT. It adds 915 tokens to every session, about $0.0046 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
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.
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 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).
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.
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.