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-build-debuggit 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-build-debug)<a href="https://agentmods.dev/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-build-debug"><img src="https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-build-debug/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-build-debug"><img src="https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-build-debug.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.00119 | $0.00572 |
| Opus 5.5 | $0.00048 | $0.00229 |
| Sonnet 5.5 | $0.00024 | $0.00114 |
| Haiku 4.5 | $0.00012 | $0.00057 |
Grade A, and why
yocto-build-debug 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 2mo 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 Build Debug
Workflow
- Identify the build entrypoint: Makefile,
kas,repo,oe-init-build-env, container script, CI job, or vendor wrapper. - Confirm
MACHINE,DISTRO,BBLAYERS,TMPDIR,DL_DIR,SSTATE_DIR, and target image/recipe. - Reproduce the smallest failing command. Prefer parse, fetch, or one task over a full image rebuild.
- Inspect logs before editing metadata. Use yocto_log_triage.py with the build directory for a quick scan.
- Classify the failure: parse, layer, provider, fetch, patch, configure, compile, install, package, QA, image, test, or signature.
- Route metadata questions to
$bitbake-metadata; route board boot/deploy issues to$yocto-deploy-flashor$yocto-bsp-bringup.
Commands
bitbake-layers show-layers
bitbake-layers show-recipes RECIPE
bitbake-layers show-appends
bitbake -e RECIPE
bitbake -c listtasks RECIPE
bitbake -c TASK -f RECIPE
bitbake -g RECIPE
bitbake-diffsigs SIGDATA_A SIGDATA_B
oe-pkgdata-util list-pkgs
References
- failure-playbook.md: failure categories and fixes.
- performance-cache.md: sstate, downloads, disk, parallelism, and reproducibility debugging.
Guardrails
- Do not recommend deleting
tmp/orsstate-cache/until narrower evidence has been checked. - Do not silence QA with
INSANE_SKIPuntil the package/file/license root cause is known. - Do not assume deploy output is under
tmp/; many builds usetmp-glibc, multiconfig paths, or customTMPDIR. - Do not change provider/version policy globally without checking affected recipes and images.
What ships with it
4 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.
- 2mo ago First seen · 42 lines · 119 tokens per session scan A c19cd9414209
yocto-build-debug is a skill published in the GitHub repository prashantdivate/awesome-yocto-ai-agent-skills (4 stars, last pushed 4mo ago), licensed MIT. It adds 119 tokens to every session and 572 once invoked, about $0.0005 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-08-31.
yocto-build-debug compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| yocto-build-debugprashantdivate/awesome-yocto-ai-agent-skills | Skill | 4 | 4mo ago | MIT | A | 119 | Codex |
| debug-taskmoonrepo/moon | Skill | 4.2k | yesterday | MIT | A | 203 | Claude Code |
| openocdzhinkgit/embeddedskills | Skill | 785 | 18d ago | MIT | A | 247 | Claude Code |
| jlinkzhinkgit/embeddedskills | Skill | 785 | 18d ago | MIT | A | 176 | Claude Code |
| eidezhinkgit/embeddedskills | Skill | 785 | 18d ago | MIT | A | 151 | Claude Code |
| netzhinkgit/embeddedskills | Skill | 785 | 18d ago | MIT | A | 234 | Claude Code |
| serialzhinkgit/embeddedskills | Skill | 785 | 18d ago | MIT | A | 137 | Claude Code |