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/.claude/commands/api-execute.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/commands/savannah-i-g/nanotracker-api-sdk/api-execute)<a href="https://agentmods.dev/commands/savannah-i-g/nanotracker-api-sdk/api-execute"><img src="https://agentmods.dev/badge/commands/savannah-i-g/nanotracker-api-sdk/api-execute/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/commands/savannah-i-g/nanotracker-api-sdk/api-execute"><img src="https://agentmods.dev/badge/commands/savannah-i-g/nanotracker-api-sdk/api-execute.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.00000 | $0.00211 |
| Opus 5.5 | $0.00000 | $0.00084 |
| Sonnet 5.5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
api-execute 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.
What it actually says
Run a batch of nanoTracker Local API commands.
Usage: /api-execute <commandsJSON> [optsJSON]
If optsJSON is omitted, a default { "undoDescription": "claude batch" }
is used. Always pick a more specific description when you can.
Run via:
node tools/cli.mjs execute '$ARGUMENTS'
The CLI splits the arguments into commands and opts (the second JSON
blob). It reads ~/.nanotracker/relay-token automatically.
Common pitfalls:
- Forgetting
opts.undoDescription→missingUndoDescriptionerror. - Using order-list index instead of
patternId→notFound. Resolve viagetPatternListfirst. - Mutating an empty pattern with thousands of
setCellops when onesetRangewould do.
See ../skills/api-author-pattern/SKILL.md
for the full command list and conventions.
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 · 27 lines · 0 tokens per session scan A 24843c8d9a9a
api-execute is a command published in the GitHub repository savannah-i-g/nanotracker-api-sdk (20 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 211 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.