NVIDIA/TensorRT-Model-Connect is a collection of C++ reference implementations for deploying supported Hugging Face models with NVIDIA TensorRT, a system that runs trained models to produce inference results. It is for developers who want to build and run supported models or evaluate model integrations through TensorRT. The catalogue entries provide skills and instructions for using this model deployment workflow.
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 skills add NVIDIA/TensorRT-Model-Connect --skill write-git-messagesgit clone --depth 1 https://github.com/NVIDIA/TensorRT-Model-ConnectWrote 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/nvidia/tensorrt-model-connect/write-git-messages)<a href="https://agentmods.dev/skills/nvidia/tensorrt-model-connect/write-git-messages"><img src="https://agentmods.dev/badge/skills/nvidia/tensorrt-model-connect/write-git-messages/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/nvidia/tensorrt-model-connect/write-git-messages"><img src="https://agentmods.dev/badge/skills/nvidia/tensorrt-model-connect/write-git-messages.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.00075 | $0.01503 |
| Opus 5.5 | $0.00030 | $0.00601 |
| Sonnet 5.5 | $0.00015 | $0.00301 |
| Haiku 4.5 | $0.00007 | $0.00150 |
Grade A, and why
write-git-messages 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 1mo 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Git Messages
Workflow
- Identify the artifact and exact comparison: commit, PR, squash/rebase message, or review response; base ref/SHA; head ref/SHA; and intended target.
- Inspect the actual change with
git status --short, `git diff --stat - Follow the repository's existing convention first. If it has no clear convention, default to Conventional Commits for commit and PR titles.
- Separate implemented behavior, static/CPU validation, target-hardware proof, model parity, package evidence, and performance/qualification. Do not promote one tier into another.
- Keep claims evidence-based. Do not invent issue numbers, benchmark results, tests, generated artifacts, reviewer decisions, or CI state.
- Return ready-to-use text followed by notes only when a limitation or choice matters.
For source rationale, read references/source-notes.md only when you need to explain or adjust the standard.
Commit Messages
Use this default shape:
type(scope): imperative summary
Why this change is needed and what behavior changes.
Mention important constraints, migrations, or risk.
Refs: #123
BREAKING CHANGE: explain incompatible behavior
Guidelines:
- Keep the first line short and self-contained; aim for 50 characters when practical.
- Separate the title from the body with a blank line.
- Use imperative mood in the summary:
add,fix,document,remove. - Use a meaningful type:
feat,fix,docs,test,refactor,perf,build,ci,chore, orrevert. - Add a scope only when it helps route ownership or understand impact.
- Put the "why" and user-visible behavior in the body; do not restate every file changed.
- Use footers for issue links, co-authors, and breaking changes.
- Do not add a co-author unless that person or tool actually authored part of the change and the user wants the attribution.
- Split unrelated work into separate commits when possible. If not possible, choose the dominant type and explain the combined scope in the body.
- Avoid vague titles such as
update files,misc fixes,work in progress, orfix stuff. - In this repo, never include
Claudein commit messages because the GitHub ruleset rejects it.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 139 lines · 75 tokens per session scan A 2998d50ad1d8
write-git-messages is a skill published in the GitHub repository NVIDIA/TensorRT-Model-Connect (276 stars, last pushed today), licensed Apache-2.0. It adds 75 tokens to every session and 1,503 once invoked, about $0.0003 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.
Other skills, from other repositories
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
pr-description-writer
Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…
ring:generating-release-guides
Generating an internal Operations-facing update/migration guide from the git diff between two refs, documenting per-change client impact, deploy ordering, monitoring, and rollback notes in English, pt-br, or both. Use when preparing a version release or recording what changed for the Ops team. Runs read-only by…
review-gate
Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…
docs
Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…
huggingface-transformers
Use when running or fine-tuning Hugging Face Transformers models in Python — pipeline() inference for text classification and generation, loading weights with AutoModel/AutoTokenizer, devicemap and dtype memory management, tokenizer usage, Trainer fine-tuning, and BGE embeddings for Chinese RAG. Covers transformers…