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.
curl -O https://raw.githubusercontent.com/tenstorrent/tt-studio/main/.claude/skills/license-attribution-compliance/SKILL.mdgit clone --depth 1 https://github.com/tenstorrent/tt-studioWrote 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.
[](https://agentmods.dev/skills/tenstorrent/tt-studio/license-attribution-compliance)<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.
<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>- NVIDIA SkillSpector pass
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 | $0.00076 | $0.00901 |
| Sonnet 5 | $0.00030 | $0.00360 |
| Haiku 4.5 | $0.00015 | $0.00180 |
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 12d 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.
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.
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.
- 12d ago First seen · 135 lines · 151 tokens per session scan A fc7ea5b9e56e
license-attribution-compliance is a skill published in the GitHub repository tenstorrent/tt-studio (50 stars, last pushed today), licensed Apache-2.0. It adds 151 tokens to every session and 1,802 once invoked, about $0.0008 per session on Opus 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.
Other skills, from other repositories
compiler-review
Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
compiler-verify
Use when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.
tamagui
Universal React UI framework for web and native. Use when building cross-platform apps with Tamagui, creating styled components with styled(), configuring design tokens/themes, using Tamagui UI components, or working with animations. Triggers: "tamagui", "styled()", "$token", "XStack/YStack", "useTheme", "@tamagui/"…
beui
Pick and install beUI (@beui) animated React components from the shadcn registry. Use when building motion UI, agent/chat interfaces, toasts, docks, bottom sheets, drawers, popovers, sliders, loaders, 404 pages, or any beui.dev component. Maps user intent to exact @beui install slugs instead of inventing custom…
beui-pro
Choose, inspect, install, and compose licensed beUI Pro premium React blocks from the authenticated shadcn registry. Use when building or improving landing pages with beUI Pro, installing @beui-pro items, selecting premium heroes, features, pricing, social proof, CTAs, navigation, footers, or other page sections, or…