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 skills/texasinstruments/tinyml-tensorlab/setupnpx skills add TexasInstruments/tinyml-tensorlab --skill setupgit clone --depth 1 https://github.com/TexasInstruments/tinyml-tensorlabWhat 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.00115 | $0.01900 |
| Opus 5 | $0.00057 | $0.00950 |
| Sonnet 5 | $0.00023 | $0.00380 |
| Haiku 4.5 | $0.00012 | $0.00190 |
Grade A, and why
setup 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TinyML Agent Skill — Setup
Run this once after installing the plugin. Re-run any time you move or reinstall tinyml-tensorlab, or want to change your update mode.
Step 1: Discover script paths
Two separate runner.py files exist — one for this setup skill, one for the main tinyml-workflow-agent skill. Find both:
Main skill scripts (SCRIPTS_DIR) — used for tinyml-tensorlab operations during this session only (not stored in .env):
find ~/.claude -name "runner.py" 2>/dev/null | grep "tinyml-workflow-agent" | head -1
Set SCRIPTS_DIR from result (strip /runner.py, keep the directory).
Setup skill scripts (SETUP_SCRIPTS_DIR) — used only during this setup:
find ~/.claude -name "runner.py" 2>/dev/null | grep "setup/scripts" | head -1
Set SETUP_SCRIPTS_DIR from result (strip /runner.py, keep the directory).
If either is not found, ask the user:
"Where is the tinyml-agent-skills plugin installed?"
Verify both runners exist:
ls "$SCRIPTS_DIR/runner.py"
ls "$SETUP_SCRIPTS_DIR/runner.py"
Step 2: Choose update mode
Ask the user:
"How would you like to manage updates for this skill?
- Pinned — stay on the current version, no automatic updates
- Auto-update — check for newer versions at the start of each session"
NOTE: Current version can be found in plugins/tinyml-agent-skills/.claude-plugin/plugin.json,
Call the setup runner (not the main skill runner) with their choice:
# Pinned:
UPDATE_RESPONSE=$(python3 "$SETUP_SCRIPTS_DIR/runner.py" set_update_mode '{"mode": "pinned"}')
# Auto-update:
UPDATE_RESPONSE=$(python3 "$SETUP_SCRIPTS_DIR/runner.py" set_update_mode '{"mode": "auto"}')
Confirm success: true from UPDATE_RESPONSE before proceeding.
Extract and store for Step 7:
UPDATE_MODE=$(echo "$UPDATE_RESPONSE" | python3 -c "import sys, json; print(json.load(sys.stdin).get('mode'))")
UPDATE_PINNED_VERSION=$(echo "$UPDATE_RESPONSE" | python3 -c "import sys, json; print(json.load(sys.stdin).get('pinned_version') or '')")
What ships with it
3 files 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.
- 2d ago First seen · 193 lines · 0 tokens per session scan A 766446ab1583
setup is a skill published in the GitHub repository TexasInstruments/tinyml-tensorlab (51 stars, last pushed 18d ago), licensed BSD-3-Clause. It adds 115 tokens to every session and 1,900 once invoked, about $0.0006 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 skills, from other repositories
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…