PlainTab: Skill for Codex

.agents/skills/commit-changes/SKILL.md

commit-changes is a skill for Codex from kaininx/PlainTab. It costs 64 tokens per session (966 once invoked), scanned A, original, MIT.

A Git workflow for preparing and creating commits in the PlainTab repository. It uses scoped Conventional Commit messages, a standard format such as `fix(module): describe the change`.

In plain words
What is it for?
Use it when staging changes, creating a commit, or writing a detailed commit subject and body. It is especially useful when the worktree contains changes from more than one task.
Why use it?
It helps keep unrelated work out of the same commit and makes commit history precise and consistent. It also checks recent commits so new messages match the repository’s style.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents); $skill-name invocation.

This is kaininx/PlainTab's own configuration. It tells Codex how to work on PlainTab itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything PlainTab configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kaininx/PlainTab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/kaininx/PlainTab/main/.agents/skills/commit-changes/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/kaininx/PlainTab

Made for: Codex.

Wrote 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.

agentmods badge for commit-changes

README.md
[![agentmods](https://agentmods.dev/badge/skills/kaininx/plaintab/commit-changes/github.svg)](https://agentmods.dev/skills/kaininx/plaintab/commit-changes)
Your own site
<a href="https://agentmods.dev/skills/kaininx/plaintab/commit-changes"><img src="https://agentmods.dev/badge/skills/kaininx/plaintab/commit-changes/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.

agentmods 80×15 button for commit-changes

Your own site · 80×15
<a href="https://agentmods.dev/skills/kaininx/plaintab/commit-changes"><img src="https://agentmods.dev/badge/skills/kaininx/plaintab/commit-changes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 966 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.00966
Opus 5.5 $0.00026 $0.00386
Sonnet 5.5 $0.00013 $0.00193
Haiku 4.5 $0.00006 $0.00097

Measured 2mo ago against content hash 9d6c62c8ba16, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

commit-changes 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 2mo 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.

.agents/skills/commit-changes/SKILL.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Commit PlainTab Changes

Use this skill to make clean PlainTab commits without mixing unrelated work.

Commit Style

  • Use scoped Conventional Commits by default: type(scope): 精准描述.
  • Allowed types include feat, fix, perf, refactor, chore, docs, test, style, and other Conventional Commit types only when they accurately describe the change.
  • Always include a scope when a clear module or area exists, for example fix(wallpaper): ..., refactor(storage): ..., docs(rules): ..., test(import-export): .... Omit scope only when the change is genuinely cross-cutting and no honest scope fits.
  • Prefer Chinese commit subjects and bodies when the user asks in Chinese.
  • Match the current repository history. Before committing, inspect recent subjects with git log --oneline -10 and keep the same Chinese Conventional Commit rhythm unless the user asks for another style.
  • Make the subject long enough to be precise. It should name the changed behavior or module and the concrete result, not just the activity. Avoid vague subjects such as fix(settings): 修复问题, docs(rules): 更新文档, or chore: 调整代码.
  • Prefer type(scope): 动词 + 具体对象/行为 + 结果/目的, for example fix(wallpaper): 补齐用户数据备份中的 IndexedDB Blob 恢复顺序.
  • The body is required for non-trivial commits. Use it to explain what changed, why it changed, how it was verified, and any storage/migration/UI risk boundary. Keep it factual and specific; do not pad with generic release-note language.
  • Write multiple body bullets when needed. A good body usually has 3-6 bullets covering:
    • the concrete code paths or modules changed;
    • the user-visible behavior or data-safety effect;
    • migration/import-export/i18n implications when relevant;
    • verification commands or focused manual checks that passed;
    • intentionally preserved limitations or excluded files.

Example:

fix(settings): 统一数据备份口令可见性并补齐导入按钮状态

- 将加密导出和 .ptab 导入口令收口到同一套显示/隐藏状态逻辑,只保留图标按钮。
- 选择 JSON 备份时保持导入口令禁用,选择 .ptab 后再启用口令输入和可见性切换。
- 复用现有口令 i18n 标签,避免新增无可见文案的显示/隐藏翻译 key。
- 验证通过 node --check js/settings-panel.js 和数据导入控件回归脚本。

Read the full file on GitHub · 59 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 2mo ago First seen · 59 lines · 64 tokens per session scan A 9d6c62c8ba16

Subscribe to this mod's changes

commit-changes is a skill published in the GitHub repository kaininx/PlainTab (96 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 966 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.