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-author-pattern/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-author-pattern)<a href="https://agentmods.dev/skills/savannah-i-g/nanotracker-api-sdk/api-author-pattern"><img src="https://agentmods.dev/badge/skills/savannah-i-g/nanotracker-api-sdk/api-author-pattern/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-author-pattern"><img src="https://agentmods.dev/badge/skills/savannah-i-g/nanotracker-api-sdk/api-author-pattern.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.00051 | $0.01369 |
| Opus 5.5 | $0.00020 | $0.00548 |
| Sonnet 5.5 | $0.00010 | $0.00274 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
api-author-pattern 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Author a pattern via the Local API
When to use
Any time you're writing pattern data — placing notes, building a
drum loop, copying / shifting cells, creating new patterns,
arranging the order list, changing tempo. All of this goes through
nanotracker_execute.
The contract
nanotracker_execute {
"commands": [ /* one or more LocalApiCommand */ ],
"opts": { "undoDescription": "human-readable label", "dryRun": false }
}
opts.undoDescriptionis required unlessdryRunis true.- Whole batch is validated, then either fully applied or fully rejected. One undo entry per batch.
- Hard limits: 10,000 commands, 64 patterns created, 1 MiB payload, 20 batches/sec.
Common cell ops
{ "op": "setCell", "patternId": 0, "row": 0, "channel": 0,
"cell": { "note": 49, "instrument": 1, "volume": 64 } }
{ "op": "setNoteOff", "patternId": 0, "row": 8, "channel": 0 }
{ "op": "clearCell", "patternId": 0, "row": 0, "channel": 0 }
{ "op": "setRange", "patternId": 0, "rowStart": 0,
"channels": [0, 1, 2],
"cells": [
[ {"note": 49, "instrument": 1, "volume": 64}, {}, {} ],
[ {}, {"note": 53, "instrument": 1, "volume": 48}, {} ]
] }
setRange is much cheaper than many setCell commands when you're
filling a region. The cells array is [row][channelIndex] where
channelIndex indexes into the channels array, not into the
project's channel list.
Note encoding
- Tracker note 1 = C-0, note 49 = C-4 (middle C, MIDI 60), note 97 = note-off, note 0 = empty.
tracker = midi - 11.volume: 0xFFmeans "use the sample's default" — not 255 dB.
Note-offs
A note-off ends the currently-playing voice on a channel. In the pattern
editor this is the == cell. Use the dedicated setNoteOff op:
{ "op": "setNoteOff", "patternId": 0, "row": 48, "channel": 0 }
It writes the canonical cell
{ note: 97, instrument: 0, volume: 0xFF, effect: 0 } — the same shape
you'd place by typing ==. setCell with { note: 97 } works too but
merges — the old instrument and volume fields stay on the cell,
which reads as a note-off that also holds an instrument, which is
almost never what you want. Prefer setNoteOff.
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 · 141 lines · 51 tokens per session scan A 1a3b2c851d8c
api-author-pattern is a skill published in the GitHub repository savannah-i-g/nanotracker-api-sdk (20 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,369 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…