Borrowing it
Nothing to install: this file belongs to Mistakey/simulink-automation-suite. 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/Mistakey/simulink-automation-suite/main/.claude/skills/live-testing/SKILL.mdgit clone --depth 1 https://github.com/Mistakey/simulink-automation-suiteWrote 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/mistakey/simulink-automation-suite/live-testing)<a href="https://agentmods.dev/skills/mistakey/simulink-automation-suite/live-testing"><img src="https://agentmods.dev/badge/skills/mistakey/simulink-automation-suite/live-testing.svg" alt="Measured on agentmods" 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.00072 | $0.00940 |
| Opus 5 | $0.00036 | $0.00470 |
| Sonnet 5 | $0.00014 | $0.00188 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
live-test 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 8d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Live Device Testing
End-to-end functional verification of the simulink-automation-suite plugin on real MATLAB/Simulink hardware. This skill tests the plugin as a user would — through its published interface, not its source code.
On-Demand References
.claude/skills/live-testing/phases.md— Detailed phase definitions, test case generation rules, pass/fail criteria, error handling. Read when starting test execution..claude/skills/live-testing/report-template.md— Report format, update rules, suggestions generation. Read when writing or updating the report (Phase 6).
Isolation Rules
PROHIBITED:
- Read simulink_cli/ source code
- Read tests/ unit tests
REQUIRED:
- Discover available actions via: python -m simulink_cli --json '{"action":"schema"}'
- Execute all tests via CLI commands
- Generate test cases dynamically from schema output
ALLOWED:
- Read skills/simulink_automation/SKILL.md (shipped skill — Phase 5 doc-accuracy target)
- Read skills/simulink_automation/reference.md (shipped reference doc)
- Read docs/reports/ (compare with previous reports)
- Read git log (determine incremental scope)
Reading the shipped skill files is a deliberate, scoped exception — the purpose is to verify that documentation actually guides users to correct results.
Test Mode Selection
When invoked, determine the test mode:
Does docs/reports/LIVE-TEST-REPORT.md exist?
├─ No → FULL test (all phases, all actions)
└─ Yes → Read report, extract test_commit and schema snapshot
Did user request "full"?
├─ Yes → FULL test
└─ No → INCREMENTAL (see Incremental Logic below)
User specifies "retest FAIL-001" or "retest Phase 3"?
└─ TARGETED test (only specified items)
Incremental Logic
1. Read test_commit from existing report
2. Run: git log {test_commit}..HEAD --oneline
3. Run: python -m simulink_cli --json '{"action":"schema"}'
4. Compare schema output with Schema Snapshot section in report
Mandatory re-tests:
- All items with status FAIL
- All items with status BLOCKED (re-check environment)
AI-judged additions:
- Commit messages reference specific actions → re-test those action's items
- skills/simulink_automation/SKILL.md changed → re-test Phase 5
- Schema output differs from snapshot → re-test Phase 1 + Phase 4
- Optionally spot-check some PASS items for regression
If changes are large-scale (refactor, new actions added to schema):
- Suggest full test to user, ask for confirmation
What ships with it
2 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.
- 8d ago First seen · 93 lines · 72 tokens per session scan A 434a13e76f45
live-test is a skill published in the GitHub repository Mistakey/simulink-automation-suite (9 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 940 once invoked, about $0.0004 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-31.
Other skills, from other repositories
jetson-video-pipeline
Use when executing and verifying Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or acceptance workflows with exact artifact handoffs.
mixed-signal-cosim
Run mixed-signal co-simulation — digital gate-level Verilog + analog behavioral models together. Use when the user says "mixed-signal sim", "co-simulation", "digital-analog integration test", or at Step A9 of the analog track.
native-sim
Host-based simulation using the Zephyr nativesim board. Covers building for Linux/macOS/Windows, automated testing, host-side debugging (GDB, Valgrind), and host-target integration. Trigger when developing application logic without hardware or setting up CI/CD tests.
android-hardware-testing
Automated UIAutomator tests and Hardware mocking setup.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.