What is license-attribution-compliance?

A license review process for keeping third-party notices correct when a project changes its dependencies or bundled files. Third-party notices explain which outside software or assets are included and under what license.

Reviewing dependency and asset changes, running the project's attribution check, classifying licenses, and updating the root license or frontend license files.

It catches missing or outdated attribution and flags license risks such as non-commercial terms, copyleft requirements, or unclear origins.

How tenstorrent/tt-studio configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to tenstorrent/tt-studio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/tenstorrent/tt-studio/main/.claude/skills/license-attribution-compliance/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/tenstorrent/tt-studio

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tenstorrent/tt-studio/license-attribution-compliance/github.svg)](https://agentmods.dev/skills/tenstorrent/tt-studio/license-attribution-compliance)

Your own site

<a href="https://agentmods.dev/skills/tenstorrent/tt-studio/license-attribution-compliance"><img src="https://agentmods.dev/badge/skills/tenstorrent/tt-studio/license-attribution-compliance/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tenstorrent/tt-studio/license-attribution-compliance"><img src="https://agentmods.dev/badge/skills/tenstorrent/tt-studio/license-attribution-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 151 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,802 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00151	$0.01802
Opus 5.5	$0.00060	$0.00721
Sonnet 5.5	$0.00030	$0.00360
Haiku 4.5	$0.00015	$0.00180

Measured 2mo ago against content hash fc7ea5b9e56e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

license-attribution-compliance scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/license-attribution-compliance/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

License Attribution Compliance

TT-Studio is Apache-2.0 © Tenstorrent AI ULC and ships under a strict regime. This skill keeps third-party attribution correct when dependencies or bundled assets change. There are two layers:

Deterministic gate — dev-tools/check_license_attribution.py, meant for CI on every PR. It catches mechanical drift: a stale frontend license file, or a newly added dependency that nobody attributed.
Judgment review (this skill) — classify the actual license, flag NonCommercial / copyleft / provenance risks, and write the attribution in the right place using the repo's established patterns.

Run the gate first, then reason about whatever it surfaces.

The repo's attribution surfaces

Surface	What it covers	How it's maintained
Root `LICENSE` → "Third-Party Dependencies" list	Notable / distributed deps + pointers	Hand-edited bullets: `- Name (SPDX) [License available here](url)`
`app/frontend/third-party-licenses.txt`	Every frontend production npm dep (full license text)	`cd app/frontend && npm run generate-license`
SPDX file headers	Every source file (`.py`, `.sh`, Dockerfile, `.ts/.tsx/.js/.jsx`)	Enforced by existing CI (`check-copyright` / ESLint `header/header-format`); fix with `python run.py --add-headers` or `npm run header:fix:changed`
(none yet) backend Python deps	"utilized but not distributed" — covered by the blanket clause in LICENSE	If a backend dep is ever distributed/bundled, it needs an explicit notice

Step 1 — run the gate

python3 dev-tools/check_license_attribution.py            # both checks
python3 dev-tools/check_license_attribution.py --check-frontend
python3 dev-tools/check_license_attribution.py --check-new-deps --base origin/main

Frontend freshness FAIL → cd app/frontend && npm run generate-license, commit the result. (Needs node; the check SKIPs where node is absent.)
New-dep attribution FAIL → continue to Step 2 for each named dep.

Read the full file on GitHub · 135 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 135 lines · 151 tokens per session scan A fc7ea5b9e56e

Subscribe to this mod's changes

license-attribution-compliance is a skill published in the GitHub repository tenstorrent/tt-studio (52 stars, last pushed yesterday), licensed Apache-2.0. It adds 151 tokens to every session and 1,802 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Frontend Legal and compliance React accelerator ai-agents backend-service chat-application ui-components

license-attribution-compliance next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
license-attribution-compliancetenstorrent/tt-studio	Skill	52	yesterday	Apache-2.0	A	151	Claude Code
compiler-reviewreact/react	Skill	252k	yesterday	MIT	A	27	Claude Code
web-design-guidelinessiberiacancode/agent-skills	Skill	23	27d ago	MIT	A	44	Claude Code, Codex
tamagui-v6-configtamagui/tamagui	Skill	14k	today	MIT	A	0	Claude Code, Codex
tamagui-theme-generatortamagui/tamagui	Skill	14k	today	MIT	A	48	Claude Code, Codex
release-safetytamagui/tamagui	Skill	14k	today	MIT	A	0	Claude Code
beuistarc007/ui-components	Skill	1.9k	yesterday	MIT	A	81	Claude Code, Codex

tt-studio: Skill for Claude Code