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-ci-releasegit 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-ci-release)<a href="https://agentmods.dev/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-ci-release"><img src="https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-ci-release/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-ci-release"><img src="https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-ci-release.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.00325 |
| Opus 5 | $0.00041 | $0.00162 |
| Sonnet 5 | $0.00016 | $0.00065 |
| Haiku 4.5 | $0.00008 | $0.00032 |
Grade A, and why
yocto-ci-release 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 12d 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 CI Release
Workflow
- Identify source orchestration:
kas,repo, submodules, manifest repo, or monorepo. - Pin every layer and external source needed for reproducibility.
- Separate caches from build output:
DL_DIR,SSTATE_DIR, hash equivalence, container caches, and artifacts. - Build the smallest useful CI matrix: parse, recipe smoke, image, SDK, QEMU/testimage, hardware smoke where available.
- Publish signed and checksummed artifacts with machine, distro, image, git refs, build config, license data, and SBOM if enabled.
- Keep secrets out of
local.conf, logs, and artifacts.
References
- ci-release-playbook.md: CI pipeline patterns, cache strategy, release artifact checklist.
Guardrails
- Do not use floating branch refs for release builds.
- Do not persist
tmp/as a cache unless the project explicitly accepts the fragility. - Do not publish images without checksums and provenance.
- Do not run hardware flashing in CI without explicit device targeting and recovery controls.
What ships with it
2 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.
- 12d ago First seen · 27 lines · 81 tokens per session scan A dbb1c5a49fcf
yocto-ci-release is a skill published in the GitHub repository prashantdivate/awesome-yocto-ai-agent-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 325 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
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
lov-release-via-cicd
A release workflow for Node, Tauri, Vite, shell, and GitHub Release projects. It checks or configures automated versioning and publishing, including macOS signing and notarisation when relevant.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…