agentleFS
imMamdouhaboammarimMamdouhaboammar/anti-slop-engineering/skills/asset-provenance-guard/SKILL.md

asset-provenance-guard

Skill4 starsChanged 31 days agoMITView on GitHub

Enforce cryptographic SHA-256 asset integrity, explicit open-source license provenance (CC0, MIT, SIL OFL, Apache 2.0), and prevent unverified external CDN hotlinks in shipping builds.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Physical Provenance Ledger: Every local image, model, font, or audio file in project asset directories must possess an entry in …

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Asset Sourcing & License Provenance Ledger Guard

Guarantee cryptographic asset integrity, eliminate copyright liabilities, and prevent unverified external CDN hotlinks across all shipping media.

Why This Skill Is Needed & Target State

AI-assisted generation frequently pulls third-party media or hallucinated assets without verification:

  1. Unverified CDN Hotlinks: Hotlinking external CDNs (images.unsplash.com, cdn.jsdelivr.net) creates production failure risks if the remote link rots or changes.
  2. Copyright Contamination: Sourcing 3D models, textures, sound effects, or typography without explicit open license records risks copyright infringement.
  3. Asset Tampering & Drift: Binary media can be silently swapped or corrupted without Git noticing binary diff details.

The target state is cryptographic provenance: every asset has an immutable SHA-256 hash, an explicit open-source license (CC0, MIT, SIL OFL, Apache 2.0), and a structured entry in .anti-slop/asset-ledger.jsonl.

Invariant Rules

  1. Physical Provenance Ledger: Every local image, model, font, or audio file in project asset directories must possess an entry in .anti-slop/asset-ledger.jsonl.
  2. Cryptographic SHA-256 Integrity: Computed file SHA-256 hashes must match the recorded ledger hash exactly.
  3. Approved Permissible License: Licenses must originate from the approved permissible catalog (CC0, MIT, OFL-1.1, Apache-2.0, Public Domain, Hand-Authored).
  4. Zero Hotlink Dependencies: Production code must bundle assets locally or reference canonical immutable CDNs; unverified third-party hotlinks are flagged.

Asset Ledger Format (.anti-slop/asset-ledger.jsonl)

{"path": "models/hero.gltf", "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855", "source_url": "https://polyhaven.com/a/hero", "license": "CC0", "attribution": "Poly Haven"}

CLI Usage

# Scan asset directories against local ledger
bunx anti-slop-engineering asset-provenance --scan assets/

# Auto-record newly authored assets as Hand-Authored
bunx anti-slop-engineering asset-provenance --scan public/ --record-missing

# Validate custom ledger file with JSON output
bunx anti-slop-engineering asset-provenance --ledger .anti-slop/asset-ledger.jsonl --json --strict

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.