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 Higangssh/yocto-agent-skills --skill yocto-bsp-kernelgit clone --depth 1 https://github.com/Higangssh/yocto-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/higangssh/yocto-agent-skills/yocto-bsp-kernel)<a href="https://agentmods.dev/skills/higangssh/yocto-agent-skills/yocto-bsp-kernel"><img src="https://agentmods.dev/badge/skills/higangssh/yocto-agent-skills/yocto-bsp-kernel/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/higangssh/yocto-agent-skills/yocto-bsp-kernel"><img src="https://agentmods.dev/badge/skills/higangssh/yocto-agent-skills/yocto-bsp-kernel.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.00075 | $0.00521 |
| Opus 5 | $0.00037 | $0.00260 |
| Sonnet 5 | $0.00015 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
yocto-bsp-kernel 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 9d 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.
What it actually says
Yocto BSP Kernel
Use this skill for machine, BSP, kernel, devicetree, and bootloader work. Verify the selected machine, enabled BSP layers, kernel provider, and deploy artifacts before changing recipes.
Evidence
Ask for or inspect:
MACHINE
conf/machine/*.conf
enabled BSP layers
PREFERRED_PROVIDER_virtual/kernel
kernel recipe and bbappends
KERNEL_DEVICETREE
defconfig or config fragments
U-Boot variables
tmp/deploy/images/<machine>/
Useful commands:
bitbake-layers show-layers
bitbake-layers show-recipes virtual/kernel
bitbake-layers show-appends | rg 'linux|kernel|u-boot'
bitbake -e virtual/kernel | rg '^(MACHINE|PREFERRED_PROVIDER|KERNEL|UBOOT|SRC_URI|S)='
bitbake -c kernel_configme virtual/kernel
bitbake -c kernel_configcheck virtual/kernel
bitbake -c menuconfig virtual/kernel
bitbake -c diffconfig virtual/kernel
bitbake -c savedefconfig virtual/kernel
Review Rules
- Machine config should express hardware policy; distro config should express product policy.
- Select kernel through
PREFERRED_PROVIDER_virtual/kernelin machine or distro policy. - Keep devicetree names aligned with kernel source and machine config.
- Use kernel config fragments or defconfig intentionally; validate with kernel config tasks.
- Verify deploy artifacts before debugging bootloader or flashing.
- Check vendor BSP branch compatibility before modernizing syntax.
References
- Read references/bsp-kernel.md.
- Read references/classes-core.md for kernel and U-Boot classes.
- Read references/migration.md for release compatibility risks.
Output
Answer with:
- selected machine and kernel provider
- BSP/layer compatibility risk
- kernel/devicetree/bootloader metadata issue
- command to validate config or deploy artifacts
- minimal metadata change
What ships with it
3 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.
- 9d ago First seen · 64 lines · 75 tokens per session scan A f8299efcfca3
yocto-bsp-kernel is a skill published in the GitHub repository Higangssh/yocto-agent-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 521 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-31.
Other skills, from other repositories
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when a device is unreachable, a user reports connectivity problems, an interface…