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/darellchua2/opencode-config-template/git-compact-commits-skillnpx skills add darellchua2/opencode-config-template --skill git-compact-commits-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/git-compact-commits-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/git-compact-commits-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/git-compact-commits-skill.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.1 | $0.00041 | $0.04271 |
| Opus 5 | $0.00020 | $0.02135 |
| Sonnet 5 | $0.00008 | $0.00854 |
| Haiku 4.5 | $0.00004 | $0.00427 |
Grade A, and why
git-compact-commits-skill 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 — 659 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I Do
I provide compact commit message authoring and CI enforcement:
- Semantic Grouping: Combine related changes into single commits by phase, concern, or module
- Compact Authoring: Write commit messages within strict word/character budgets (150-word body, 72-char subject)
- CI Enforcement: Configure commitlint with custom word-count plugin and GitHub Actions workflow
- Local Enforcement: Pre-commit hook alternative for local validation
This is a guidance + enforcement skill — I teach compact authoring AND provide the CI/CD config to enforce it.
For commit type definitions and scope conventions, see git-semantic-commits.
For the full release pipeline (PR titles, merge strategy, release tags), see semantic-release-convention.
When to Use Me
Use this skill when:
- Writing commit messages that need to stay within word/character limits
- Grouping multiple related file changes into a single commit
- Setting up commitlint with word-count enforcement in GitHub Actions
- Creating a local pre-commit hook for message length validation
- Preparing commits before a squash-merge PR workflow
Authority Boundaries
| Concern | Authority Skill | Role |
|---|---|---|
| Commit types, scopes, breaking changes | git-semantic-commits |
Format definition |
| Release pipeline, PR titles, merge strategy | semantic-release-convention |
CI/CD workflow |
| Length budgets, grouping, compact writing | git-compact-commits (this skill) |
Config details |
| commitlint config with extended rules | git-compact-commits (this skill) |
Enforcement rules |
Scope: Two Use Cases
This skill targets both commit scenarios in a squash-merge workflow:
1. Branch Commits (Pre-Squash)
Individual commits during development on a feature branch. These keep git log readable during code review and make git rebase -i easier.
feat(auth): add JWT token refresh and session store
Implement automatic token refresh when access token expires.
Add session storage for persisting auth state across reloads.
Refs: BT-54
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 · 659 lines · 41 tokens per session scan A 6f5896765783
git-compact-commits-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 41 tokens to every session and 4,271 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
push
Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create a pull request.
ship
Commit, push, create PR, then after approval check CI and merge. Use when work is done and ready to ship.
dependabot-consolidator
Consolidate a repository's open Dependabot PRs into one tested branch and PR, grouping by ecosystem and risk, verifying with baseline-diff gates, and closing out on operator approval. Use when a repo has multiple open Dependabot PRs to batch, when consolidating dependency bumps into a single reviewable PR, or when…
ship
Use when ready to ship code to remote — handles direct push to main and PR-based feature branch flows. Do NOT use for partial workflows like just committing or just pushing.
git-ship
自动化 Git 工作流一键发布助手，执行完整的「ship」流程： 基于最新 main 切新分支 → commit → 推送 → 创建 PR → squash merge → 回 main。 调用 ship 本身就是对完整流程的授权；自动推断分支名、commit message 和 PR 内容， 并主动解决 Git 冲突、测试、lint、类型检查、构建和 CI 失败，持续修复和重试， 直到改动成功合并。不要因可自行修复的失败暂停，只在认证、权限、仓库保护等 无法由当前环境解决的外部阻塞出现时请求用户介入。 仅在用户明确表达「ship」意图时触发，例如： 直接说「ship」「/ship」「git ship」 明确要求完整走完 git…
jig-conformance-audit
Use to check whether a repository's history actually followed the jig procedure: conventional squash subjects, Release-Grade trailers on unreleased work, version tag format and placement, the main/develop fast-forward invariant, and a committed rubric. Read-only, exits non-zero on violations, and runs in CI.