agentleFS
narenaryannarenaryan/agent-skills/skills/security/rbvm-asset-evidence/SKILL.md

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.

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
  1. Distinctive:

    Run the synthetic freshness contract from the repository root:

    line 29

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

EntityPreserveReject as sole identity
Runtime instanceTenant/account, region/cluster, immutable provider ID or Kubernetes UIDIP, display name
ArtifactDigest, descriptor media type, platform; component coordinatesMutable image tag
ObservationSource, collection time, ingestion time, coverage, raw evidence referenceLatest database update time
FindingInstance/artifact, component, vulnerability, detector, observationCVE alone

Recipe

  1. Normalize identifiers without discarding original values. Keep instance-to-artifact and artifact-to-component edges separately; one image can serve many workloads.
  2. Reconcile only strong identifiers within their authority scope. Queue ambiguous matches; do not merge on matching hostnames. Record merge evidence and reversible lineage.
  3. 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.
  4. Preserve contradictory observations with provenance. Missing authentication, excluded paths, partial inventories, and failed collectors mean unknown coverage, not absence.
  5. Emit affected-instance counts, owner routing, and an explicit unknown/stale queue. Decide applicability with rbvm-applicability only 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.py

Sources: 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.