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 skills add matlab/matlab-agentic-toolkit --skill matlab-model-serdes-systemsgit clone --depth 1 https://github.com/matlab/matlab-agentic-toolkitWrote 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/matlab/matlab-agentic-toolkit/matlab-model-serdes-systems)<a href="https://agentmods.dev/skills/matlab/matlab-agentic-toolkit/matlab-model-serdes-systems"><img src="https://agentmods.dev/badge/skills/matlab/matlab-agentic-toolkit/matlab-model-serdes-systems/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/skills/matlab/matlab-agentic-toolkit/matlab-model-serdes-systems"><img src="https://agentmods.dev/badge/skills/matlab/matlab-agentic-toolkit/matlab-model-serdes-systems.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.00173 | $0.04405 |
| Opus 5.5 | $0.00069 | $0.01762 |
| Sonnet 5.5 | $0.00035 | $0.00881 |
| Haiku 4.5 | $0.00017 | $0.00441 |
Grade A, and why
matlab-model-serdes-systems 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 1mo 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
12 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.
- manifest.yaml 1000 B
- reference/channel-modeling.md 7.8 KB
- reference/common-mistakes.md 28 KB
- reference/custom-datapath-blocks.md 13 KB
- reference/equalization-tuning.md 11 KB
- reference/optimization.md 9.0 KB
- reference/programmatic-ami-generation.md 25 KB
- reference/serdes-api-reference.md 28 KB
- reference/serdes-utilities.md 10 KB
- reference/simulink-serdes-simulation.md 19 KB
- reference/visualization-and-metrics.md 20 KB
- reference/waveform-processing.md 7.8 KB
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.
- 1mo ago First seen · 226 lines · 173 tokens per session scan A 4513573b0e08
matlab-model-serdes-systems is a skill published in the GitHub repository matlab/matlab-agentic-toolkit (1,194 stars, last pushed 7d ago), with no licence file. It adds 173 tokens to every session and 4,405 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
simulink-configure-model-for-code-generation
Configure Simulink models for Embedded Coder (ERT), Simulink Coder (GRT rapid-prototyping), or AUTOSAR code generation. Use when the user asks to generate embedded C or C++ code, run a full build of a model, produce a code generation report, configure a model for production/ECU deployment or rapid-prototyping code…
simulink-optimizing-embedded-code
Optimizes Simulink models for Embedded Coder generated code. Use when asked to optimize or improve generated code, or reduce code metrics for a Simulink model. Targets: execution time, memory footprint (RAM, ROM, stack, data copies), code size, MISRA compliance, or any semantically similar generated-code metric. Works…
simulink-configure-real-time-target
Manage Simulink Real-Time target computers from MATLAB — list available targets, check whether a target is connected, read its lifecycle status, add/remove/rename targets, set IP addresses and credentials, choose the default target, install TLS material, configure a startup application, and run target lifecycle ops…
simulink-control-motors
Build motor control solutions using Motor Control Blockset for PMSM, induction motors, BLDC, and SynRM. Implement field oriented control, sensorless FOC, six-step control, speed control, current control, and torque control. Configure SVPWM, flux weakening, MTPA, MTPV, control of non-linear motors, inverter control…
simulink-customize-a2l
Customize A2L (ASAP2) files generated from Simulink models using coder.asap2 and coder.mapping APIs. Use this skill when adding COMPUMETHODs, creating GROUPs, converting STDAXIS to COMAXIS, adding BITOPERATIONs, creating VARIANTCODING, excluding measurements or struct elements, removing DEFAULTEVENTLIST, or any A2L…
simulink-author-classic-autosar-swc
Use this skill when authoring, reworking, or validating a Classic AUTOSAR software component (SWC) in Simulink, including autosar.api mappings, runnables, timing events, sender-receiver ports, client-server operations, IRVs, BSW service callers, and component ARXML updates.