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 easyzoom/aix-skills --skill unity-ceedling-integrationgit clone --depth 1 https://github.com/easyzoom/aix-skillsWrote 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/easyzoom/aix-skills/unity-ceedling-integration)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/unity-ceedling-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/unity-ceedling-integration/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/easyzoom/aix-skills/unity-ceedling-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/unity-ceedling-integration.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.00041 | $0.00662 |
| Opus 5.5 | $0.00016 | $0.00265 |
| Sonnet 5.5 | $0.00008 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
unity-ceedling-integration 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Ceedling Integration
Overview
Use this skill to add embedded C tests with Unity assertions, Ceedling builds, and CMock-generated mocks while keeping hardware code behind clear seams. Good embedded tests isolate logic from registers, clocks, and interrupts without pretending the hardware does not exist.
When To Use
Use this skill when:
- The user wants unit tests for C firmware, drivers, protocol parsers, state machines, or business logic.
- The issue involves Ceedling project setup, include paths, mocks, fixtures, test runners, coverage, or CI.
- The codebase uses vendor HALs, RTOS wrappers, static functions, compile-time flags, or hardware registers.
Do not use this skill for hardware-in-the-loop validation alone. Pair it with the relevant hardware or protocol skill.
First Questions
Ask for:
- Toolchain, host OS, Ceedling version, compiler, and CI environment.
- Code under test, dependencies, include paths, and hardware/HAL boundaries.
- Whether mocks, fakes, or real modules should be used.
- Build variants, configuration headers, and preprocessor flags.
- Current failing command and full test output.
Integration Checklist
-
Identify testable units. Start with pure logic, parsers, state machines, and error handling before register-level code.
-
Define hardware boundaries. Wrap HAL calls, RTOS calls, time, logging, and storage behind interfaces that can be mocked or faked.
-
Configure Ceedling deliberately. Set source paths, include paths, defines, vendor files, and plugins in
project.yml. -
Write tests around behavior. Prefer input/output and state transitions over checking private implementation details.
-
Use CMock where it clarifies intent. Mock external collaborators, but use small fakes for stateful dependencies when expectations become brittle.
-
Add CI and coverage last. Keep the command non-interactive and fast enough to run on every change.
Common Failures
- Tests include vendor headers that require target-only compiler extensions.
- Static functions are tested directly instead of through behavior.
- Mocks over-specify call order and make refactors painful.
- Configuration macros differ between tests and firmware builds.
- Global state is not reset in
setUportearDown. - CI uses a different Ruby, compiler, or path layout than local runs.
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 · 83 lines · 41 tokens per session scan A 2e1fe6f263a9
unity-ceedling-integration is a skill published in the GitHub repository easyzoom/aix-skills (38 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 662 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-09-03.
Other skills, from other repositories
hdl-module-design
Use when writing, refactoring, or deciding how to test an HDL module, component, or IP block (ROHD, Chisel, SpinalHDL, Verilog, VHDL) and you need it parameterized, validated, and covered by exhaustive tests rather than a one-off.
agent-evals
Build automated evaluation suites for AI agents using golden datasets, rubrics, and regression gates. Use when shipping agent features, validating prompt changes, or gating deployments on quality.
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
review-ugc-render
Mandatory pre-publish review gate for a UGC video render. Transcribes the finished render's AUDIO with Whisper and word-diffs it against the approved spoken script, then gates pinning the final render (videoprojectupsert patch.finalrenderid) — blocking a render whose generated audio mis-voices a word (e.g. the…
test-generator
A test-writing helper that creates unit or integration tests from the code's actual behavior and contracts. Unit tests check small pieces of code, while integration tests check how real components work together.
vitest
Set up Vitest testing in any project — detects type (Cloudflare Workers, React, Node, library), generates vitest.config.ts, test setup, utilities, and a sample test. Covers mocking patterns, coverage config, workspace setup, Jest migration. Use whenever the user mentions adding tests, setting up Vitest, configuring…