rbvm-asset-evidence
Skill0 starsChanged 40 days agoMITView on GitHub
Use when scanner findings must be joined to ephemeral assets, duplicate hosts, image tags, ownership, or exposure evidence with conflicting timestamps or stale inventory.
In this repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- postgres-locking-joinsSkill
- ai-bug-patternsSkill
- compressed-ndjson-boundariesSkill
- http-resume-integritySkill
- linux-io-latency-triageSkill
- macos-disk-space-recoverySkill
- minimal-sufficient-evidenceSkill
- modularize-large-filesSkill
- patch-reproducer-validitySkill
- prompt-cache-boundariesSkill
- proton-drive-selective-backupSkill
- transactional-outbox-deliverySkill
- conventional-commitsSkill
- git-advanced-mergingSkill
- git-bisect-forensicsSkill
- git-data-recoverySkill
- git-hooksSkill
- git-rerereSkill
- git-reset-mechanicsSkill
- git-revisions-syntaxSkill
- git-rewriting-historySkill
- git-submodulesSkill
- git-worktreesSkill
- github-ssh-keysSkill
- npm-publish-ci-pitfallsSkill
- sapling-stacked-pr-workflowSkill
- go-concurrency-patternsSkill
- go-data-idiomsSkill
- go-error-handlingSkill
- go-interfaces-embeddingSkill
- go-pprof-profilingSkill
- marketing-funnel-diagnosisSkill
- marketing-geo-experimentsSkill
- marketing-incrementalitySkill
- marketing-positioning-testsSkill
- python-descriptors-mroSkill
- python-logging-cookbookSkill
- python-scaling-regression-testsSkill
- python-unicode-gotchasSkill
- rust-compile-time-invariantsSkill
- rust-deterministic-concurrency-testsSkill
- rust-error-identity-boundariesSkill
- rust-regex-search-contractsSkill
- rust-runtime-bug-classesSkill
- rust-tokio-actor-deliverySkill
- rust-tokio-cancellation-safetySkill
- sales-discovery-qualificationSkill
- sales-mutual-action-plansSkill
- sales-pipeline-forecast-calibrationSkill
- sales-value-negotiationSkill
- ai-triage-evaluationSkill
- container-image-patchingSkill
- dependency-artifact-integritySkill
- dnssec-sentinel-diagnosticsSkill
- iam-policy-change-replaySkill
- rbvm-applicabilitySkill
- rbvm-guarded-remediationSkill
- rbvm-priority-decisionsSkill
- rbvm-risk-exceptionsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Run the synthetic freshness contract from the repository root:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
RBVM Asset Evidence
An asset is an incarnation, an artifact is content, and an observation is a time-bounded claim. Never collapse those identities into an IP address, tag, or hostname.
Join contract
| Entity | Preserve | Reject as sole identity |
| Runtime instance | Tenant/account, region/cluster, immutable provider ID or Kubernetes UID | IP, display name |
| Artifact | Digest, descriptor media type, platform; component coordinates | Mutable image tag |
| Observation | Source, collection time, ingestion time, coverage, raw evidence reference | Latest database update time |
| Finding | Instance/artifact, component, vulnerability, detector, observation | CVE alone |
Recipe
- Normalize identifiers without discarding original values. Keep instance-to-artifact and artifact-to-component edges separately; one image can serve many workloads.
- Reconcile only strong identifiers within their authority scope. Queue ambiguous matches; do not merge on matching hostnames. Record merge evidence and reversible lineage.
- Define policy-owned freshness budgets per evidence class. Evaluate collection age, not ingestion age; reject future timestamps beyond approved clock tolerance. Recollect after deployment, routing, ownership, or configuration changes.
- Preserve contradictory observations with provenance. Missing authentication, excluded paths, partial inventories, and failed collectors mean unknown coverage, not absence.
- Emit affected-instance counts, owner routing, and an explicit unknown/stale queue. Decide applicability with
rbvm-applicabilityonly after identity is bounded.
Example: pod checkout is recreated with UID B after UID A was scanned. Its unchanged name and IP do not transfer A's clean result. Link B to its observed image digest, retain A historically, and request B's runtime/configuration evidence.
Run the synthetic freshness contract from the repository root:
python3 skills/security/rbvm-asset-evidence/fixture.pySources: Kubernetes object identity and OCI descriptor v1.1.1, reviewed 2026-10-10. Freshness budgets and reconciliation gates are local policy, not standards; details in SOURCES.md.
Pitfalls
- Reused IPs can transfer remediation evidence to the wrong machine.
- An image-index digest and platform-manifest digest identify different objects; retain their relationship.
- A fresh ingestion timestamp cannot rejuvenate an old scan.
- Collector silence cannot prove retirement or successful remediation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

