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/tinyml-workflow-agentnpx skills add TexasInstruments/tinyml-tensorlab --skill tinyml-workflow-agentgit 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.00086 | $0.08681 |
| Opus 5 | $0.00043 | $0.04340 |
| Sonnet 5 | $0.00017 | $0.01736 |
| Haiku 4.5 | $0.00009 | $0.00868 |
Grade C, and why
tinyml-workflow-agent scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Delete the project: `rm -rf "$CCS_PROJECT_PATH"` How it starts
The opening of the file, as written. The whole thing — 789 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tiny ML Tensorlab Skill
Overview
Build, train, compile, and deploy ML models to embedded MCUs using Tiny ML tensorlab.
CRITICAL: Script and Path Locations
runner.py and SCRIPTS_DIR are in THIS SKILL directory, NOT in tinyml-tensorlab.
When setting up:
SCRIPTS_DIR=<path-to-this-skill>/scripts
# runner.py is at:
$SCRIPTS_DIR/runner.py
Do NOT use:
~/tinyml-tensorlab/scripts/(wrong — this doesn't exist)~/tinyml-tensorlab/tinyml-modelmaker/scripts/(wrong)
Use:
~/.claude/plugins/marketplaces/<plugin_name>/skills/<skill_name>/scripts/(correct — this is the skill)
Workflow (13 steps):
- Session setup — load
.env, activate venv, check for updates. If not set up, run/tinyml-agent-skills:setupfirst. - Requirements — task type, device, data type, channel count
- Common section — task_type + target_device → save to WORK_DIR
- Dataset validation — validate format, get effective path
- Dataset section — generate YAML → save to WORK_DIR
- Feature extraction and Data Processing transforms
- Step 6A: Analyze dataset for statistical insights
- Step 6B: Get recommendations → generate YAML → save to WORK_DIR
- Model selection — analyze dataset size → rank models
- Training section — model name + hyperparams → save to WORK_DIR
- Testing section — testing config → save to WORK_DIR
- Compilation section — preset selection → save to WORK_DIR
- Assemble config — combine all sections → write config.yaml
- Run training — execute run_tinyml_modelzoo.sh
- Deploy to device — create CCS project → flash IMPORTANT: After EACH step which generates a section of the config file, pause and show the user the config file (created thus far) and proceed only with user's approval of the config. Reference guides (read on demand, not upfront):
references/config_creation_guide.md— task types, devices, YAML rulesreferences/example_running_guide.md— run commands, monitoring, troubleshootingreferences/device_deployment_guide.md— CCS project, flashing, validation
What ships with it
31 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.
- evals/device_deployment_evals.json 1.4 KB
- evals/evals.json 1.3 KB
- references/config_creation_guide.md 10 KB
- references/deployment_sdk_reference.md 2.2 KB
- references/device_deployment_guide.md 8.8 KB
- references/documentation_guide.md 23 KB
- references/example_running_guide.md 9.0 KB
- references/FE_and_Data_Processing_Transforms/Data_processing_transforms.md 1.9 KB
- references/FE_and_Data_Processing_Transforms/FE_transforms.md 14 KB
- references/installation_env_variables_guide.md 5.3 KB
- references/log_streaming_pattern.md 6.4 KB
- references/tensorlab_constants_guide.md 4.5 KB
- scripts/__init__.py 0 B runs code
- scripts/common_section_tools.py 8.0 KB runs code
- scripts/compilation.py 13 KB runs code
- scripts/config_file_tools.py 8.7 KB runs code
- scripts/constants.py 6.3 KB runs code
- scripts/dataset_analysis.py 5.2 KB runs code
- scripts/dataset_format_tools.py 26 KB runs code
- scripts/dataset_section_tools.py 7.4 KB runs code
- scripts/device_deployment.py 33 KB runs code
- scripts/feature_extraction.py 39 KB runs code
- scripts/feature_schema.py 4.3 KB runs code
- scripts/model_selection_tools.py 25 KB runs code
- scripts/preset_ranker.py 7.5 KB runs code
- scripts/run_with_log_stream.sh 1.1 KB runs code
- scripts/runner.py 9.6 KB runs code
- scripts/schema.yaml 22 KB
- scripts/testing.py 5.0 KB runs code
- scripts/training_section_tools.py 17 KB runs code
- scripts/update_manager.py 6.1 KB runs code
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 · 789 lines · 86 tokens per session scan C 1181835897d1
tinyml-workflow-agent is a skill published in the GitHub repository TexasInstruments/tinyml-tensorlab (51 stars, last pushed 18d ago), licensed BSD-3-Clause. It adds 86 tokens to every session and 8,681 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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…