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 bitbake-metadatagit 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/bitbake-metadata)<a href="https://agentmods.dev/skills/prashantdivate/awesome-yocto-ai-agent-skills/bitbake-metadata"><img src="https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/bitbake-metadata/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/bitbake-metadata"><img src="https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/bitbake-metadata.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.00100 | $0.00693 |
| Opus 5 | $0.00050 | $0.00347 |
| Sonnet 5 | $0.00020 | $0.00139 |
| Haiku 4.5 | $0.00010 | $0.00069 |
Grade A, and why
bitbake-metadata 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BitBake Metadata
Core Workflow
- Determine the release and BitBake version from the workspace before applying syntax guidance. Check
bitbake --version, branch names,LAYERSERIES_COMPAT, and the docs selected by the parent Yocto release. - Inspect existing metadata first. Search for the recipe, provider, class, variable, override, task, and package name across all configured layers.
- Read official docs for the exact mechanism. Use bitbake_doc_router.py with a topic name to choose a starting URL.
- Explain metadata changes in terms of parse-time effects, task effects, package effects, and signature/sstate effects.
- Validate with BitBake introspection rather than assumptions.
Introspection Commands
Use the project wrapper if one exists. Otherwise, after sourcing the build environment:
bitbake-layers show-layers
bitbake-layers show-recipes RECIPE
bitbake-layers show-appends
bitbake -e RECIPE | less
bitbake -c listtasks RECIPE
bitbake -g RECIPE
bitbake-dumpsig SIGDATA_OR_SIGINFO
bitbake-diffsigs SIGDATA_A SIGDATA_B
For targeted variable checks, prefer bitbake -e RECIPE and search for the final assignment plus history comments.
Metadata Editing Rules
- Preserve local style for variable operators, override order, indentation, and layer layout.
- Prefer
:append,:prepend, and:removeoverride syntax for modern releases, but verify old-release syntax before changing legacy branches. - Keep machine, distro, image, and recipe concerns in their correct files.
- Use
.bbappendwhen changing recipes from another layer. - Keep checksums, licenses, and
SRC_URIchanges explicit and reviewable. - Do not set
PREFERRED_PROVIDER,PREFERRED_VERSION,BBMASK, or global variables without checking blast radius.
References
Read only the reference file needed for the task:
- official-sources.md: authoritative BitBake docs and source links.
- metadata-cheatsheet.md: syntax, operators, overrides, tasks, and fetcher reminders.
- debugging.md: parse, fetch, task, dependency, QA, signature, and sstate debugging workflow.
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 · 56 lines · 100 tokens per session scan A 4cc5c6bb1039
bitbake-metadata is a skill published in the GitHub repository prashantdivate/awesome-yocto-ai-agent-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 100 tokens to every session and 693 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…