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/beriberikix/zephyr-agent-skills/testing-debuggingnpx skills add beriberikix/zephyr-agent-skills --skill testing-debugginggit clone --depth 1 https://github.com/beriberikix/zephyr-agent-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/beriberikix/zephyr-agent-skills/testing-debugging)<a href="https://agentmods.dev/skills/beriberikix/zephyr-agent-skills/testing-debugging"><img src="https://agentmods.dev/badge/skills/beriberikix/zephyr-agent-skills/testing-debugging.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 | $0.00072 | $0.00685 |
| Opus 5 | $0.00036 | $0.00342 |
| Sonnet 5 | $0.00014 | $0.00137 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
testing-debugging 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 5d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zephyr Testing & Debugging
Ensure code quality and system reliability using Zephyr's comprehensive testing framework and observability tools.
Core Workflows
1. Ztest Framework
Write robust unit and integration tests for native simulation and real hardware.
- Reference: ztest_framework.md
- Key Tools:
ZTEST_SUITE,ZTEST,zassert_equal.
2. Twister Test Runner
Automate test execution across multiple platforms and generate professional reports.
- Reference: twister_testing.md
- Key Tools:
twisterscript,testcase.yaml, hardware mapping.
3. Tracing & Debugging
Analyze system behavior, timing, and memory usage with advanced tracing tools.
- Reference: tracing_debugging.md
- Key Tools:
CONFIG_TRACING, Segger SystemView, Thread Analyzer.
Quick Start (Ztest)
#include <zephyr/ztest.h>
ZTEST_SUITE(basic_test, NULL, NULL, NULL, NULL, NULL);
ZTEST(basic_test, test_pass) {
zassert_true(true, "Boolean evaluation failed");
}
Professional Patterns (Reliability)
- Continuous Integration: Integrate Twister reports (
twister.json) into CI/CD pipelines for automated regression testing. - HIL Validation: Use hardware maps to consistently run critical hardware tests on real devices during every release cycle.
- Stack Safety: Always enable
CONFIG_STACK_SENTINELand the Thread Analyzer during development to catch memory issues early.
Automation Tools
- twister_smoke.py: Run a small Twister suite and print result summary.
Examples & Templates
- testcase.yaml.template: Starter testcase metadata for Twister.
Validation Checklist
-
twisterexecutes selected test suites with no unexpected failures. - At least one
ZTESTsuite runs in simulation and reports pass/fail correctly. - Tracing or thread-analyzer output is captured and reviewed for hotspots.
- CI artifacts include machine-readable reports (for example
twister.json).
What ships with it
6 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.
- 5d ago First seen · 65 lines · 72 tokens per session scan A b3b03a37b4fe
testing-debugging is a skill published in the GitHub repository beriberikix/zephyr-agent-skills (62 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 685 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-30.
Other skills, from other repositories
verify
Verify that a change really works before you claim completion.
moai-ref-testing-pyramid
Test pyramid strategy, coverage targets, test patterns, and quality metrics reference. Agent-extending skill that amplifies manager-develop test-creation and quality-validation work with production-grade testing patterns. NOT for: production code implementation, architecture design, DevOps, security audits.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
nw-fp-fsharp
F# language-specific patterns, Railway-Oriented Programming, and Computation Expressions.
nw-fp-kotlin
Kotlin language-specific patterns with Arrow, Raise DSL, and coroutine-based effects.
nw-hexagonal-testing
5-layer agent output validation, I/O contract specification, vertical slice development, and test doubles policy with per-layer examples.