matlab-testing-ci

matlab-testing-ci is a skill for Claude Code, Codex from wzyn20051216/matlab-agent-skills. It costs 62 tokens per session (1,075 once invoked), scanned A, original, MIT.

A workflow for checking MATLAB and Simulink code, models, results, and generated files. It covers unit tests, regression checks, coverage, reports, and automated runs in GitHub Actions.

In plain words
What is it for?
Use it to test MATLAB scripts and functions, validate Simulink models and simulations, measure coverage, create test artifacts, and set acceptance checks for GitHub projects.
Why use it?
It helps catch broken calculations, simulations, or generated outputs before work is considered complete. The same checks can run locally and in continuous integration, which is automated checking after code changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to test MATLAB scripts and functions, validate Simulink models and simulations, measure coverage, create test artifacts, and set acceptance checks for GitHub projects.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wzyn20051216/matlab-agent-skills/matlab-testing-ci
Install

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.

Any agent
npx skills add wzyn20051216/matlab-agent-skills --skill matlab-testing-ci
Clone the repo
git clone --depth 1 https://github.com/wzyn20051216/matlab-agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for matlab-testing-ci

README.md
[![agentmods](https://agentmods.dev/badge/skills/wzyn20051216/matlab-agent-skills/matlab-testing-ci/github.svg)](https://agentmods.dev/skills/wzyn20051216/matlab-agent-skills/matlab-testing-ci)
Your own site
<a href="https://agentmods.dev/skills/wzyn20051216/matlab-agent-skills/matlab-testing-ci"><img src="https://agentmods.dev/badge/skills/wzyn20051216/matlab-agent-skills/matlab-testing-ci/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.

agentmods 80×15 button for matlab-testing-ci

Your own site · 80×15
<a href="https://agentmods.dev/skills/wzyn20051216/matlab-agent-skills/matlab-testing-ci"><img src="https://agentmods.dev/badge/skills/wzyn20051216/matlab-agent-skills/matlab-testing-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,075 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.01075
Opus 5.5 $0.00025 $0.00430
Sonnet 5.5 $0.00012 $0.00215
Haiku 4.5 $0.00006 $0.00108

Measured 4d ago against content hash c8f236b89898, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

matlab-testing-ci 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 4d 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.

skills/matlab-testing-ci/SKILL.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MATLAB Testing CI

Use this skill to close the loop on MATLAB work.

Test Ladder

Start as small as possible, then broaden:

  1. Smoke script runs without error.
  2. One unit test checks a core numeric result.
  3. Project or folder tests pass with runtests.
  4. Simulink model simulates and logged signals are checked.
  5. CI workflow runs the same command.

For MATLAB or Simulink engineering tasks, completion means the work has been self-checked after writing:

  1. Scripts/functions run without error.
  2. Simulink models load and update/compile without diagram errors.
  3. Simulations reach the requested stop time.
  4. Key logged signals are nonempty and finite.
  5. Generated figures/data/reports exist and are nonempty.
  6. If code generation or deployment is requested, generated code/project/binary artifacts are checked for existence and nonzero size.
  7. If any step cannot be completed, record the exact blocker, the command that failed, and the highest-value next action.

MATLAB Unit Test Pattern

Use:

results = runtests;
assertSuccess(results);

For scripts, add explicit assertions instead of only checking that MATLAB exits.

CI Pattern

For GitHub Actions, use MathWorks maintained actions:

  • matlab-actions/setup-matlab@v3
  • matlab-actions/run-tests@v3
  • matlab-actions/run-command@v3

Use self-hosted runners for private licenses, specialized toolboxes, hardware, or long simulations.

Artifact Requirements

Save:

  • MATLAB command log.
  • Test results or summary JSON.
  • Figures, models, generated code, and reports.
  • MATLAB release and toolbox inventory.
  • Dataset or paper reproduction manifest.

Acceptance Report

End every task with:

  • Command executed.
  • Passed checks.
  • Skipped checks and reason.
  • Artifact folder.
  • Next highest-value regression test.

Three Questions, Three Answers

"It ran", "the number is right" and "the requirement is met" are different claims, and Phase 3A/3B produced every combination of them. mas_grade keeps them apart:

Read the full file on GitHub · 122 lines

Changes

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.

  1. 4d ago Changed · +50 lines · -4 tokens per session c8f236b89898
  2. 1mo ago First seen · 72 lines · 66 tokens per session scan A 3cfc32b8299d

Subscribe to this mod's changes

matlab-testing-ci is a skill published in the GitHub repository wzyn20051216/matlab-agent-skills (27 stars, last pushed 5d ago), licensed MIT. It adds 62 tokens to every session and 1,075 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.

Related

Other skills, from other repositories

testing

Use this skill when writing, fixing, reviewing, or planning tests in any project, in whatever runner the project already uses. Also use it to write the failing proof for a suspected bug and to promote that proof into a durable regression test. Triggers: user says "test", "unit test", "integration test", "e2e", "mock"…

WrongStack/WrongStack · 116 tokens

proof-strategy

Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".

tonone-ai/tonone · 53 tokens

proof-recon

Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".

tonone-ai/tonone · 50 tokens

matlab-run-tests

Run MATLAB test suites and analyze results, including test filtering, parallel execution, result diagnostics, code coverage collection, gap analysis, and CI/CD with buildtool. Use when running tests, filtering test suites, analyzing test failures, checking, collecting, or analyzing coverage, justifying uncovered code…

matlab/matlab-agentic-toolkit · 96 tokens

unit-testing

Unit testing patterns with Vitest - mocking, fixtures, isolation, and fast feedback.

LiorCohen/sdd · 20 tokens

Verification & Quality Assurance

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

ruvnet/ruflo · 36 tokens