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-layer-reviewgit 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-layer-review)<a href="https://agentmods.dev/skills/higangssh/yocto-agent-skills/yocto-layer-review"><img src="https://agentmods.dev/badge/skills/higangssh/yocto-agent-skills/yocto-layer-review/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-layer-review"><img src="https://agentmods.dev/badge/skills/higangssh/yocto-agent-skills/yocto-layer-review.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.00081 | $0.00598 |
| Opus 5 | $0.00041 | $0.00299 |
| Sonnet 5 | $0.00016 | $0.00120 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
yocto-layer-review 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Yocto Layer Review
Use this skill to review layers and diagnose metadata visibility problems. Layer issues often look like recipe, provider, or package failures; prove whether BitBake sees the metadata first.
Required Evidence
Ask for or inspect:
conf/layer.conf
conf/bblayers.conf
bitbake-layers show-layers
bitbake-layers show-recipes <recipe>
bitbake-layers show-appends
bitbake-layers show-overlayed
Layer Checklist
Review:
BBPATH .= ":${LAYERDIR}"
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend"
BBFILE_COLLECTIONS += "mylayer"
BBFILE_PATTERN_mylayer = "^${LAYERDIR}/"
BBFILE_PRIORITY_mylayer = "6"
LAYERSERIES_COMPAT_mylayer = "scarthgap wrynose"
LAYERDEPENDS_mylayer = "core"
Check:
- collection name is unique and stable
LAYERSERIES_COMPAT_*matches the target release- required layers are declared with
LAYERDEPENDS_* - recipe and append globs cover intended files
BBFILE_PRIORITY_*is not used to hide provider/version policy problems- optional bbappends use
BBFILES_DYNAMICwhen the target layer may be absent .bbappendfilename matches an existing recipe version or intentionally uses%
Common Problems
- layer is present in the tree but missing from
bblayers.conf .bbappendsilently not applied due to recipe version mismatch- collection name in
BBFILES_DYNAMICdoes not match target layer collection - layer priority causes a recipe to win unexpectedly
- vendor BSP layer pins an older release and rejects modern syntax
- dependency layer missing even though a recipe path exists locally
References
- Read references/official-doc-map.md for official layer docs.
- Read references/yocto-field-guide.md for layer and provider basics.
- Read references/migration.md for release compatibility checks.
Output
Answer with:
- whether BitBake sees the layer and append
- exact layer.conf or filename issue
- metadata visibility command to prove it
- minimal fix
- validation command
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.
- 11d ago First seen · 71 lines · 81 tokens per session scan A cf9428b6e691
yocto-layer-review is a skill published in the GitHub repository Higangssh/yocto-agent-skills (8 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 598 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…