Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/tenstorrent/tt-studio/draft-release-notesnpx skills add tenstorrent/tt-studio --skill draft-release-notesgit 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/draft-release-notes)<a href="https://agentmods.dev/skills/tenstorrent/tt-studio/draft-release-notes"><img src="https://agentmods.dev/badge/skills/tenstorrent/tt-studio/draft-release-notes.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00121 | $0.01290 |
| Opus 5 | $0.00060 | $0.00645 |
| Sonnet 5 | $0.00024 | $0.00258 |
| Haiku 4.5 | $0.00012 | $0.00129 |
Grade A, and why
draft-release-notes 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 4d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TT-Studio Release Notes Drafting
Follow this when asked to draft release notes for a new TT-Studio version. The goal is notes that read exactly like the previous few releases — same sections, same voice, same level of detail — built from the actual changes on the release branch.
Inputs to confirm
- New version (e.g.
v2.9.0) and the release branch (e.g.rc-v2.9.0). - Previous version it ships after (e.g.
v2.8.0). If not given, it's the most recent published GitHub release.
If the user names a branch, use it. Don't guess a version — ask if unclear.
The release PR into main is titled Rc vX.Y.Z (the Lint PR title check is
skipped for rc-* head branches) or release: vX.Y.Z — see CONTRIBUTING →
Release Process. Step 2 relies on that Rc vX.Y.Z merge-commit title as the
cutoff.
Step 1 — Study the previous releases (match the style, don't invent it)
Read the most recent two or three published release descriptions so the new one matches their structure and voice:
# needs no auth:
WebFetch https://github.com/tenstorrent/tt-studio/releases
The established house style is:
- A header line:
## :rocket: TT Studio <version> is out! - A lead-in:
A few highlights since <previous version>: - Three sections, in this order, each only if it has content:
### 🚀 New Features— bold feature name + one-line description### 🐛 Bug Fixes— one line each, past tense ("Fixed…", "Resolved…")### 🔧 Technical Improvements— internal/infra/CI/refactor/dep bumps
- A closing
Full changelog → <link>line.
Bold-name-plus-description is the signature of the New Features section — keep it. Bug Fixes and Technical Improvements are plain one-liners.
Step 2 — Gather the actual changes
Fetch the release branch and list every commit since the previous release. Each
release's RC merge commit is titled like Rc vX.Y.Z (#NNNN) — the previous
release's merge commit is the cutoff; everything above it is new.
git fetch origin <release-branch>
git log origin/<release-branch> --oneline -60
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.
- 4d ago First seen · 134 lines · 121 tokens per session scan A f365611f9ad9
draft-release-notes is a skill published in the GitHub repository tenstorrent/tt-studio (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 121 tokens to every session and 1,290 once invoked, about $0.0006 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
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/"…
git-safety
Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.
release-safety
Release safety rules. INVOKE WHEN: yarn release, npm publish, release canary, release packages, publishing, skip checks, skip tests. NEVER skip checks or tests without explicit permission.
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…
analytical-table
Use ALWAYS for AnalyticalTable internals — react-table v7 plugin architecture, vendored react-table code at packages/main/src/components/AnalyticalTable/react-table/, tableHooks, AnalyticalTableHooks, useDynamicColumnWidths, useColumnResizing, useRowSelect, useF2CellEdit, useManualRowSelect…