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 prashantdivate/awesome-yocto-ai-agent-skills --skill yocto-kernel-bspgit clone --depth 1 https://github.com/prashantdivate/awesome-yocto-ai-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/prashantdivate/awesome-yocto-ai-agent-skills/yocto-kernel-bsp)<a href="https://agentmods.dev/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-kernel-bsp"><img src="https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-kernel-bsp/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/prashantdivate/awesome-yocto-ai-agent-skills/yocto-kernel-bsp"><img src="https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-kernel-bsp.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.00093 | $0.00577 |
| Opus 5 | $0.00046 | $0.00289 |
| Sonnet 5 | $0.00019 | $0.00115 |
| Haiku 4.5 | $0.00009 | $0.00058 |
Grade A, and why
yocto-kernel-bsp 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 11d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Yocto Kernel BSP
Core Workflow
- Identify the Yocto release,
MACHINE, BSP layer, kernel provider, and kernel recipe before editing. - Inspect existing machine configuration, kernel recipe,
.bbappend, device tree, defconfig, and config fragments. - Prefer the product BSP layer for local changes. Avoid editing upstream
poky,meta,meta-yocto, OE-Core, or vendor layers unless preparing an upstreamable patch. - Separate concerns:
- Machine selection belongs in
conf/machine/*.conf. - Kernel source/provider policy belongs in distro or machine config only when locally justified.
- Kernel config belongs in fragments or defconfig according to the project's existing style.
- Device tree changes belong near existing DTS/DTSI structure or in a layer-local patch.
- Machine selection belongs in
- Validate with BitBake and kernel tasks before claiming success.
Commands
bitbake-layers show-recipes virtual/kernel
bitbake-layers show-appends
bitbake -e virtual/kernel
bitbake virtual/kernel
bitbake -c menuconfig virtual/kernel
bitbake -c diffconfig virtual/kernel
bitbake -c deploy virtual/kernel
Use yocto_kernel_doc_router.py with a topic name for official documentation links.
References
- kernel-bsp-workflows.md: provider discovery, recipe/appends, fragments, and validation.
- device-tree-checklist.md: DTB selection, DTS/DTSI origin, patch workflow, and deploy checks.
- machine-config-checklist.md: machine variables, provider policy, overrides, and board variants.
Guardrails
- Do not assume
linux-yoctobehavior applies to vendor kernels without checking the recipe/classes. - Do not mix board variants that have different RAM, boot media, storage, or DTBs.
- Do not change
PREFERRED_PROVIDER_virtual/kernel,KERNEL_DEVICETREE, orCOMPATIBLE_MACHINEglobally unless the blast radius is understood. - Do not hand-edit generated kernel build output as a permanent fix; add patches, fragments, or metadata in the owning layer.
What ships with it
5 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.
- 11d ago First seen · 46 lines · 93 tokens per session scan A 92235a2454f7
yocto-kernel-bsp is a skill published in the GitHub repository prashantdivate/awesome-yocto-ai-agent-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 93 tokens to every session and 577 once invoked, about $0.0005 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
eide
A build tool for EIDE projects, an embedded-development extension for Visual Studio Code. It finds EIDE project settings and builds firmware using ARM CC or GCC.
workflow
A workflow skill for embedded-device projects that plans and runs building, flashing, debugging, observing, and diagnosis tasks.
robot-perception
Comprehensive best practices for robot perception systems covering cameras, LiDARs, depth sensors, IMUs, and multi-sensor setups. Use this skill when working with RGB image processing, depth maps, point clouds, sensor calibration (intrinsic, extrinsic, hand-eye), object detection, semantic segmentation, 3D…
robotics-software-principles
Foundational software design principles applied specifically to robotics module development. Use this skill when designing robot software modules, structuring codebases, making architecture decisions, reviewing robotics code, or building reusable robotics libraries. Trigger whenever the user mentions SOLID principles…
robotics-design-patterns
Architecture patterns, design principles, and proven recipes for building robust robotics software. Use this skill when designing robot software architectures, choosing between behavioral frameworks, structuring perception-planning-control pipelines, implementing state machines, designing safety systems, or…
robotics-testing
Testing strategies, patterns, and tools for robotics software. Use this skill when writing unit tests, integration tests, simulation tests, or hardware-in-the-loop tests for robot systems. Trigger whenever the user mentions testing ROS nodes, pytest with ROS, launchtesting, simulation testing, CI/CD for robotics, test…