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/skills/api-inspect-state/SKILL.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/skills/savannah-i-g/nanotracker-api-sdk/api-inspect-state)<a href="https://agentmods.dev/skills/savannah-i-g/nanotracker-api-sdk/api-inspect-state"><img src="https://agentmods.dev/badge/skills/savannah-i-g/nanotracker-api-sdk/api-inspect-state/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/savannah-i-g/nanotracker-api-sdk/api-inspect-state"><img src="https://agentmods.dev/badge/skills/savannah-i-g/nanotracker-api-sdk/api-inspect-state.svg" alt="Reviewed on agentmods" width="80" 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.00048 | $0.00767 |
| Opus 5.5 | $0.00019 | $0.00307 |
| Sonnet 5.5 | $0.00010 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
api-inspect-state 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 2mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inspect a live nanoTracker session
When to use
Use this any time you need to know what's in the project — what patterns exist, what cells they hold, what samples are loaded, what the song tempo is — before suggesting or making a change.
Cheap before expensive
Call queries in this order. Stop as soon as you have what you need.
nanotracker_health— confirm the page is connected.nanotracker_read { op: "getProjectSummary" }— bpm, speed, channels, pattern count, sample count.nanotracker_read { op: "getPatternList" }— every pattern'sid,name, row count, filled-cell count, order-list positions.nanotracker_read { op: "getRange", patternId, rowStart, rowEnd, channels? }— slice of cells. Prefer this overgetPatternfor surveys.nanotracker_read { op: "getPattern", patternId }— only when you really need every cell of a pattern.
patternId, not order-list index
Pattern ids are persistent. Order-list positions are not. The order
list maps positions → pattern ids; multiple positions can reference
the same pattern. Always resolve via getPatternList first.
// WRONG — assumes order list position 0 is pattern id 0
nanotracker_read { "op": "getPattern", "patternId": 0 }
// RIGHT — discover, then read
const list = nanotracker_read { "op": "getPatternList" }
const first = list.data[0].id
nanotracker_read { "op": "getPattern", "patternId": first }
Cell shape
{
note: number // 0 empty, 1-96 = C-0..B-7, 97 = note-off
instrument: number // 0 empty, 1-31 = sample slot
volume: number // 0xFF = use default, 0x00-0x40 = override
effect: number
effectParam: number
}
volume === 0xFF means "use the sample's stored default", not 255 dB.
Don't render it as 255 in user-facing output.
Channels are 0-indexed
channels[0] is the leftmost track. project.channels is the count
(1..32).
Empty cells are common and not a problem
Most cells in a fresh pattern have note: 0, instrument: 0, volume: 0xFF, effect: 0, effectParam: 0. Treat that as "empty" — don't
report it as data.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 87 lines · 48 tokens per session scan A 22b9a3956b03
api-inspect-state is a skill published in the GitHub repository savannah-i-g/nanotracker-api-sdk (20 stars, last pushed 6mo ago), licensed MIT. It adds 48 tokens to every session and 767 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…