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/brianmontanaweb/agentic-design-system/commit-messagenpx skills add brianmontanaweb/agentic-design-system --skill commit-messagegit clone --depth 1 https://github.com/brianmontanaweb/agentic-design-systemWhat 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.00051 | $0.00738 |
| Opus 5 | $0.00026 | $0.00369 |
| Sonnet 5 | $0.00010 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
commit-message 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 2d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message
Draft a commit message for the current changes given $ARGUMENTS (optional: --commit to also create the commit).
Gotchas
- Draft-only by default — output the message; do not run
git commitunless--commitwas passed. - Staged changes win — if anything is staged, describe only the staged diff; otherwise describe all uncommitted changes (and say which set you used).
- Match history, not a generic convention — read recent
git logsubjects before writing; this repo's style is authoritative over any general conventional-commits habit. - Never invent scope from a single stray file — scope reflects where the substance of the change lives; a drive-by fix in a second area goes in the body, not the scope.
Step 1 — Collect the change
git status --short
git diff --staged --stat # if anything is staged
git diff --stat # otherwise
git log --oneline -15
Read the full diff (git diff --staged / git diff) for the files that carry the substance of the change. Skim generated files (packages/tokens/src/generated.ts, snapshots) — name them in the body if regenerated, but do not describe their contents line by line.
Step 2 — Choose type and scope
Format: type(scope): subject — scope omitted when the change is repo-wide.
| Type | Used for |
|---|---|
feat |
New component, prop, token, skill, or capability |
fix |
Bug or violation fix (a11y fixes count) |
refactor |
Restructuring with no behavior change |
chore |
Tooling, lint config, versioning, baselines |
test |
Test or eval additions/changes |
build |
Bundling, packaging, build order |
docs |
Spec docs or markdown-only changes |
Scopes seen in history: skills, lint, core, evals, plus package names (tokens, agents) and component names where the change is that narrow. Multi-part changes may join two clauses with ; in the subject (see 142a14c).
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.
- 2d ago First seen · 65 lines · 51 tokens per session scan A fb7155c0ec47
commit-message is a skill published in the GitHub repository brianmontanaweb/agentic-design-system (2 stars, last pushed 13d ago), licensed MIT. It adds 51 tokens to every session and 738 once invoked, about $0.0003 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-31.
Other skills, from other repositories
animal-island-ui-style
Build React UIs in the animal-island-ui style — an Animal Crossing-inspired component library (warm earth tones, pill shapes, 3D game-button depth, soft motion). Use when (1) building pages or components with the animal-island-ui npm package in a React project; (2) generating a standalone single-file HTML page in this…
ng-blatui
Use the ng-blatui Angular UI library in an app — install, import components (bui-prefixed, signal-based, zoneless, SSR-safe), theme with Tailwind v4 + oklch tokens, localize dates/numbers/labels, and discover the full catalog via the registry, api.json, llms.txt or the ng-blatui-mcp MCP server. Invoke when building…
vuetify0
Use when building Vue 3 UI in this repo or any v0 consumer — and when about to write a native , a homemade setTimeout timer, or a homemade overlay/dialog. Those are Button, useTimer, and Dialog/Popover/useStack; do not roll them. Also selection, forms, registries, virtual scroll, popovers, focus, snackbars, SSR…
releasing
Authoring a changeset, or cutting a release for @vuetify/v0 and the @paper/ design systems. Use when writing a .changeset/.md file, deciding what belongs in changelog copy, re-entering or exiting changesets pre/beta mode, or reviewing a Version Packages PR. Covers the changeset content contract, the two version…
angular-best-practices
Official Angular v22 coding best practices — signals, standalone, native control flow, zoneless, host bindings, Signal Forms, inject(), and accessibility (WCAG AA / AXE). Use whenever writing, generating, or reviewing Angular/TypeScript code in this repo.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for…