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-security-compliancegit 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-security-compliance)<a href="https://agentmods.dev/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-security-compliance"><img src="https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-security-compliance/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-security-compliance"><img src="https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-security-compliance.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.00085 | $0.00457 |
| Opus 5 | $0.00043 | $0.00229 |
| Sonnet 5 | $0.00017 | $0.00091 |
| Haiku 4.5 | $0.00009 | $0.00046 |
Grade A, and why
yocto-security-compliance 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 Security Compliance
Core Workflow
- Identify Yocto release, image, recipe, package names, source version, and patch state.
- Verify current vulnerability/security facts online when the user asks about CVEs, fixes, exploitability, support status, or latest security data.
- Distinguish recipe name, source package name, runtime package name, binary package name, and CVE product/vendor names.
- Inspect upstream source, local patches, license files, package manifests, SPDX/SBOM output, and
cve-checkoutput before changing metadata. - Prefer recipe upgrades or patch backports over blanket ignores.
- Document compliance decisions in the layer or release notes where the project expects them.
Use yocto_security_doc_router.py with a topic name for official documentation links.
References
- cve-workflow.md: CVE investigation, patch/backport, and false-positive handling.
- license-compliance.md:
LICENSE,LIC_FILES_CHKSUM, manifests, and incompatible license policy. - sbom-spdx-workflow.md: SPDX/SBOM generation, provenance, and release review.
Guardrails
- Do not suppress CVE, license, or QA findings without documenting the exact reason.
- Do not change
LICENSE,LIC_FILES_CHKSUM, or CVE status fields without inspecting upstream source, patches, and package output. - Do not treat build-time package names, runtime package names, source recipe names, and CVE product names as interchangeable.
- Do not put signing keys, embargoed details, or private vulnerability data into public layers or logs.
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.
- 12d ago First seen · 31 lines · 85 tokens per session scan A f84778bae222
yocto-security-compliance is a skill published in the GitHub repository prashantdivate/awesome-yocto-ai-agent-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 457 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
lov-china-website-filing
A workflow for preparing and launching websites in mainland China, including ICP filing and public-security filing. ICP filing is the registration required for many mainland websites, while public-security filing is a separate police registration.
lov-review-doc
A contract review assistant for agreements such as NDAs, service contracts, data agreements, employment contracts, licences, and investment documents. It can analyse risks, add comments, and suggest revised wording.
contract-review-pro
Professional-grade contract review skill that adds comment-based issue annotations without changing original text. Enforces a four-layer review (entity verification, basic, business, legal), writes structured comments (issue type, risk reason, revision suggestion) with risk level encoded via reviewer name, and…
lov-public-security-filing
A guided workflow for applying for Chinese public-security internet filing after a website has passed ICP filing and is publicly accessible in mainland China. ICP filing is the earlier Chinese registration required for many mainland websites; public-security filing is a separate police-record process.
lov-legal-pages
A website content tool that drafts privacy policy and terms-of-service pages from the project’s real business and data-handling facts. These pages explain how a service uses information and what rules apply to its users.
lov-domain-cutover
A workflow for putting a mainland-China website online after its ICP filing is approved. It verifies the deployment, DNS, HTTPS certificate, domain response, ICP footer, and handling of the old domain.