plugin-scanner uses the published HCS-28 baseline adapter catalog for bundled Codex skills. The scanner does not define a private skill trust profile. Instead, it computes local bundled-skill evidence using the HCS-28 adapter ids, weights, contribution modes, and aggregation rules.
- Specification:
HCS-28 - Specification version:
0.1 - Profile:
hcs-28/baseline - Related publication model:
HCS-26
The normative adapter ids and weights come directly from HCS-28:
| Adapter ID | Weight | Contribution Mode |
|---|---|---|
verification.review-status |
0.50 |
universal |
verification.publisher-bound |
0.20 |
universal |
verification.repo-commit-integrity |
0.40 |
universal |
verification.manifest-integrity |
0.30 |
universal |
verification.domain-proof |
0.10 |
universal |
metadata.links |
0.30 |
universal |
metadata.description |
0.25 |
universal |
metadata.taxonomy |
0.20 |
universal |
metadata.provenance |
0.25 |
universal |
upvotes |
1.00 |
conditional |
safety.cisco-scan |
1.00 |
universal |
repository.health |
1.00 |
conditional |
The scanner runs bundled skill trust in read mode with includeExternal=false. That means the HCS-28 aggregation algorithm stays the same, but local evidence substitutes for external refresh-only signals where possible.
Local bundled-skill normalization:
verification.review-status:100only when the local bundled skill package explicitly declaresverified=true; otherwise0verification.publisher-bound:100when plugin author metadata existsverification.repo-commit-integrity:100when bundled skill metadata declares bothrepoandcommitverification.manifest-integrity:100when every bundledSKILL.mdparses and includes required frontmatter fieldsverification.domain-proof:100when homepage and repository hosts alignmetadata.links: exact HCS-28 baseline rulemetadata.description: exact HCS-28 description-length thresholdsmetadata.taxonomy: exact HCS-28 tag-count and language-count matrixmetadata.provenance: exact HCS-28 repo/commit ruleupvotes: omitted in the denominator unless a local upvote count is providedsafety.cisco-scan: exact HCS-28 severity normalization when Cisco results exist; otherwise universal0repository.health: omitted in read mode unless a persisted external score exists
The scanner follows HCS-28 normalization and denominator rules exactly:
- Clamp emitted component values to
[0,100]. - Materialize missing universal components as
0. - Compute each adapter total as the arithmetic mean of its component values.
- Include conditional adapters in the denominator only when they emit scores.
- Compute the composite total as the weighted mean of included adapter totals.
This keeps bundled skill trust explainable and directly comparable to the published HCS-28 baseline semantics without referencing private registry implementation details.