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/rust-works/succinctly/commit-msgnpx skills add rust-works/succinctly --skill commit-msggit clone --depth 1 https://github.com/rust-works/succinctlyWhat 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.00054 | $0.00586 |
| Opus 5 | $0.00027 | $0.00293 |
| Sonnet 5 | $0.00011 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
commit-msg 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message Skill
Generates and improves commit messages following conventional commits format.
Conventional Commits Format
<type>(<scope>): <description>
[optional body]
[optional footer]
Types
| Type | Use For |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Formatting, no code change |
refactor |
Code change that neither fixes a bug nor adds feature |
perf |
Performance improvement |
test |
Adding or updating tests |
chore |
Maintenance tasks |
ci |
CI/CD changes |
build |
Build system changes |
Scopes
See .omni-dev/scopes.yaml for the canonical,
enforced scope list — do not duplicate it here.
Examples
Feature Addition
feat(json): add PFSM table-driven parser
Implements parallel finite state machine approach from hw-json-simd.
Achieves 880 MiB/s throughput on x86_64 (AMD Zen 4), 40-77% faster than scalar.
Bug Fix
fix(bp): correct find_close for edge case at word boundary
Fixes #42
Performance Improvement
perf(popcount): add AVX-512 VPOPCNTDQ implementation
5.2x faster than scalar for large bitvectors.
Requires Intel Ice Lake+ or AMD Zen 4+.
Refactoring
refactor(jq): replace deprecated last() with next_back()
Removes dead code and simplifies iterator handling.
Instructions
- Read the staged changes with
git diff --cached - Understand what changed and why
- Choose appropriate type and scope
- Write a concise subject line (50 chars ideal, 72 max)
- Add body if changes need explanation
- Include footer for breaking changes or issue references
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 · 93 lines · 54 tokens per session scan A b86e510205f8
commit-msg is a skill published in the GitHub repository rust-works/succinctly (51 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 586 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…