Maintain AlbumentationsX license, CLA, provenance notices, and packaged legal artifacts consistently.

AGPL-3.0Auto-check passedAI & LLM Engineering

Install License Integrity

skills CLI
$ npx skills add albumentations-team/AlbumentationsX --skill license-integrity -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install albumentations-team/AlbumentationsX license-integrity --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/albumentations-team/AlbumentationsX.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/license-integrity .claude/skills/license-integrity && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
license-integrity
GitHub stars
567
Token cost
~1.3k tokens
SKILL.md length
628 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Maintain AlbumentationsX license, CLA, provenance notices, and packaged legal artifacts consistently.

  • Works in 7 steps: docs/maintaining/license-provenance.md → LICENSE → LICENSING.md → …
  • Tasks that involve Computer vision
  • SKILL.md covers Required Context, Invariants, Library Procurement and… and Verification
  • Calls uv

What it does

License Integrity is an agent skill from albumentations-team/AlbumentationsX. Maintain AlbumentationsX license, CLA, provenance notices, and packaged legal artifacts consistently.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering, covering Computer vision and Deep learning. The repository describes itself as: Image augmentation for computer vision. AGPL-3.0-only or commercial licensing. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve Computer vision
  • Tasks that involve Deep learning

Example prompts

  • “/license-integrity”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. docs/maintaining/license-provenance.md
  2. LICENSE
  3. LICENSING.md
  4. THIRD_PARTY_NOTICES.md
  5. CLA.md
  6. legal/cla/archive/MANIFEST.md
  7. the relevant packaging, contribution, release, and public-copy files

What it can do on your machine

Read from SKILL.md and the folder at commit acee073. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

License Integrity loads about 1.3k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 628 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~30
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from albumentations-team/AlbumentationsX at commit acee073, republished under its AGPL-3.0 licence (© albumentations-team). 628 words, ~1,328 tokens.

Download SKILL.mdSave it as .claude/skills/license-integrity/SKILL.md (or your agent's skills folder).
name
license-integrity
description
Maintain AlbumentationsX license, CLA, provenance notices, and packaged legal artifacts consistently.

License Integrity

Use this skill for any change to LICENSE, CLA.md, license history, third-party notices, package license metadata, contributor acceptance language, or public repository license wording. Also use it for library procurement and privacy disclosures.

Required Context

For licensing, CLA, provenance, or packaging changes, read these files completely before editing:

  1. docs/maintaining/license-provenance.md
  2. LICENSE
  3. LICENSING.md
  4. THIRD_PARTY_NOTICES.md
  5. CLA.md
  6. legal/cla/archive/MANIFEST.md
  7. the relevant packaging, contribution, release, and public-copy files

For dependency registry changes, also read LICENSE_POLICY.md and docs/maintaining/dependency-license-review.md. The required registry covers the locked base runtime graph, including transitive and marker-selected packages. Extras are out of scope unless a package is also in that graph. Keep vulnerability-audit coverage separate; its dependency set may include extras that the license registry excludes.

Invariants

  • Default repository SPDX expression is AGPL-3.0-only.
  • The AGPL permits commercial use subject to its terms. Do not use the words commercial, proprietary, internal, or production as automatic license triggers.
  • Separately negotiated commercial terms grant alternative permissions only for their stated scope. Do not promise support, warranties, maintenance, or an SLA unless an executed agreement or order form includes it.
  • Keep LICENSE byte-identical to the complete canonical GNU AGPL version 3 text; keep the repository expression and commercial-license path in LICENSING.md.
  • Do not remove the exact legacy Albumentations 2.0.8 MIT notice or describe the successor license as retroactive.
  • CLA acceptance is version-specific. Archive every operative byte version, record its SHA-256 identifier, and require explicit acceptance of a new version.
  • An Entity Acceptance covers only exact named legal entities and contributors within the signer's documented authority.
  • Release artifacts contain the four outbound license/provenance files and do not contain the inbound CLA or private acceptance records.
  • Build into a fresh directory outside the checkout. A source distribution must not contain local build-output directories or nested release artifacts.
Show full SKILL.md (331 more words)Show less

Library Procurement and Privacy Copy

For prose-only changes, read the owning documents and the implementation behind the affected claims. The full legal context and artifact checks apply when the change also touches licensing, provenance, or package metadata.

  • Describe the product as the AlbumentationsX Python library running in the customer's environment. Lead purchasing copy with product fit, license coverage, and the next step. Include limitations when they affect the buyer's decision or answer a specific question; do not add speculative warnings or repeat security/privacy caveats throughout licensing and procurement pages.
  • AX owns its library assessment documents: LICENSING.md, SECURITY.md, docs/privacy.md, and docs/maintaining/. Link to the owning document instead of copying another procedure.
  • albumentations.ai is AX's project website. Preserve relevant website links, including documentation, benchmarks, Explore, newsletters, licensing, and funding. Website sign-in, accounts, and saved user content are separate from library execution and the commercial license; do not present them as AX requirements or license features. Keep the official contact vladimir@albumentations.ai.
  • Keep telemetry to a brief README mention linking to docs/privacy.md, which owns the collected fields and global opt-out instructions. API parameter docs explain the control and link to that notice. Do not repeat telemetry copy in licensing or general procurement pages; answer explicit buyer questions in their assessment documents.
  • Verify telemetry disclosures against the event model, collectors, backend, and pre-import opt-out behavior. A persistent random UUID is not proof of anonymity. Telemetry remains default-on with opt-out; its use is limited to product analysis and development, not prospect identification or sales.
  • Describe the analytics provider in docs/privacy.md as the current implementation. Keep general product wording independent of the provider. When providers change, update the relevant facts and account for versions still using the previous service.
  • Provider retention, storage region, deletion, certifications, and operational practices need evidence beyond source code. Do not turn an unverified target or a questionnaire question into a public assurance or recurring manual duty.

Verification

Run the focused checks first:

bash
uv run python tools/verify_legal_integrity.py
uv run pytest -q tests/test_legal_integrity.py
artifact_dir="$(mktemp -d)"
uv build --out-dir "${artifact_dir}"
uv run python tools/verify_legal_integrity.py --artifacts "${artifact_dir}"/*.whl "${artifact_dir}"/*.tar.gz
uv run twine check "${artifact_dir}"/*

Then run the repository quality gate required by the surrounding change.

© albumentations-team, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/license-integrity of albumentations-team/AlbumentationsX.

Open the folder on GitHubat commit acee073

Compare with similar skills

License Integrity next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

License Integrity compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
License Integrity this skillalbumentations-team/AlbumentationsX567—~1.3kAutomated safety check: PassAGPL-3.0
Segment Anything Model GuideOrchestra-Research/AI-Research-SKILLs13k8 repos~3.3kAutomated safety check: PassMIT
CLIP Image-Text MatchingOrchestra-Research/AI-Research-SKILLs13k7 repos~1.7kAutomated safety check: PassMIT
Kaiming HeK-Dense-AI/mimeo282—~1.6kAutomated safety check: PassMIT
Matlab Analyze Spectral Imagesmatlab/matlab-agentic-toolkit1.1k—~3.7kAutomated safety check: PassCustom licence
Matlab Process Imagesmatlab/matlab-agentic-toolkit1.1k—~3.7kAutomated safety check: PassCustom licence

Similar skills

  • Segment Anything Model Guide

    Orchestra-Research/AI-Research-SKILLs

    Guide to using Meta's Segment Anything Model for zero-shot image segmentation with point, box or mask prompts, or automatic mask generation.

    13k GitHub starsUsed in 8 repos~3.3k tokens
    AI & LLM EngineeringAuto-check passed
  • CLIP Image-Text Matching

    Orchestra-Research/AI-Research-SKILLs

    Explains OpenAI's CLIP model for zero-shot image classification, image-text similarity, semantic image search and content moderation, with install steps and code patterns.

    13k GitHub starsUsed in 7 repos~1.7k tokens
    AI & LLM EngineeringAuto-check passed
  • Kaiming He

    K-Dense-AI/mimeo

    Applies the reasoning style of Kaiming He, computer vision pioneer and creator of ResNet.

    282 GitHub stars~1.6k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check passed
  • Matlab Analyze Spectral Images

    matlab/matlab-agentic-toolkit

    Work with hyperspectral and multispectral images in MATLAB. An agent skill from matlab/matlab-agentic-toolkit.

    1.1k GitHub stars~3.7k tokensUpdated 2 days ago
    AI & LLM EngineeringAuto-check passed
  • Matlab Process Images

    matlab/matlab-agentic-toolkit

    Load this first for any task involving images, pictures, photos, scans, frames, volumes, or visual data — including reading, writing, filtering, enhancing, denoising, sharpening, deblurring…

    1.1k GitHub stars~3.7k tokensUpdated 2 days ago
    AI & LLM EngineeringAuto-check passed
  • Scholar Compute

    joshzyj/open-scholar-skill

    Design and execute computational social science analyses across 11 modules: text-as-data/NLP (STM, BERTopic, Wordfish, BERT, conText embedding regression, LLM annotation + DSL bias correction…

    168 GitHub stars~15k tokensUpdated 22 days ago
    AI & LLM EngineeringAuto-check passed

More from albumentations-team/AlbumentationsX

All 10 skills in this repo
  • Mixing Transforms

    albumentations-team/AlbumentationsX

    Policy for AlbumentationsX transforms that combine multiple images or objects.

    567 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Release Notes

    albumentations-team/AlbumentationsX

    Generate release notes for AlbumentationsX. An agent skill from albumentations-team/AlbumentationsX.

    567 GitHub stars~685 tokensUpdated today
    Auto-check passed
  • Performance Optimization

    albumentations-team/AlbumentationsX

    Systematic performance audit for AlbumentationsX runtime code.

    567 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Add Transform

    albumentations-team/AlbumentationsX

    Full checklist for adding a new transform to AlbumentationsX.

    567 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Docstring Deep Dive

    albumentations-team/AlbumentationsX

    Review public AlbumentationsX docstrings for useful descriptions, runnable examples, parameter semantics, and related transforms.

    567 GitHub stars~534 tokensUpdated today
    Auto-check passed
  • Validate And Fix

    albumentations-team/AlbumentationsX

    After completing code changes, runs tests and pre-commit, then iteratively fixes failures until all pass.

    567 GitHub stars~847 tokensUpdated today
    Auto-check passed

Questions about License Integrity

What does License Integrity do?

Maintain AlbumentationsX license, CLA, provenance notices, and packaged legal artifacts consistently. License Integrity is an agent skill from albumentations-team/AlbumentationsX. Maintain AlbumentationsX license, CLA, provenance notices, and packaged legal artifacts consistently.

When should I use License Integrity?

License Integrity fits situations like: tasks that involve Computer vision; tasks that involve Deep learning.

How do I install License Integrity in Claude Code?

Run `npx skills add albumentations-team/AlbumentationsX --skill license-integrity -a claude-code`. Or copy the skill folder (.codex/skills/license-integrity in albumentations-team/AlbumentationsX) into .claude/skills/license-integrity in your project. Claude Code loads it when a task matches its description.

How do I install License Integrity in Codex?

Run `npx skills add albumentations-team/AlbumentationsX --skill license-integrity -a codex`. Or copy the skill folder (.codex/skills/license-integrity in albumentations-team/AlbumentationsX) into .agents/skills/license-integrity in your project. Codex loads it when a task matches its description.

Can I use License Integrity in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add albumentations-team/AlbumentationsX --skill license-integrity -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/license-integrity, .gemini/skills/license-integrity, .github/skills/license-integrity and .opencode/skills/license-integrity in your project.

What does License Integrity need to run?

Going by SKILL.md and its folder, License Integrity needs the command-line tools its instructions call (uv). Our summary lists: Python 3.

Does License Integrity access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is License Integrity safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does License Integrity use?

License Integrity is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does License Integrity use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to License Integrity?

Skills that share tags, products or a category with License Integrity: Segment Anything Model Guide (Orchestra-Research/AI-Research-SKILLs, 13k stars), CLIP Image-Text Matching (Orchestra-Research/AI-Research-SKILLs, 13k stars), Kaiming He (K-Dense-AI/mimeo, 282 stars) and Matlab Analyze Spectral Images (matlab/matlab-agentic-toolkit, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains License Integrity?

albumentations-team (a GitHub organization) maintains it in albumentations-team/AlbumentationsX, which has 567 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 11, 2026.

Source: albumentations-team/AlbumentationsX on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.