Zen is a self-hosted notes application that stores Markdown notes inside SQLite and provides full-text search in a single Go binary. It is for people who want a lightweight notes system with low resource use. The catalogue includes agents and an instruction for working with it.
Borrowing it
Nothing to install: this file belongs to sheshbabu/zen. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sheshbabu/zen/master/.claude/skills/commit-message/SKILL.mdgit clone --depth 1 https://github.com/sheshbabu/zenWrote 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/sheshbabu/zen/commit-message)<a href="https://agentmods.dev/skills/sheshbabu/zen/commit-message"><img src="https://agentmods.dev/badge/skills/sheshbabu/zen/commit-message/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/sheshbabu/zen/commit-message"><img src="https://agentmods.dev/badge/skills/sheshbabu/zen/commit-message.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.00639 |
| Opus 5.5 | $0.00018 | $0.00256 |
| Sonnet 5.5 | $0.00009 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
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 3d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 3d ago Changed · +1 lines 01352676d36b
- 1mo ago First seen · 45 lines · 44 tokens per session scan A 64d65e7785a5
commit-message is a skill published in the GitHub repository sheshbabu/zen (1,194 stars, last pushed 4d ago), licensed AGPL-3.0. It adds 44 tokens to every session and 639 once invoked, about $0.0002 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-09-26.
Other skills, from other repositories
re0-git
Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story. User-invoked: run it after a commit.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
git-workflow
Automate the complete Git development workflow — create feature branches with conventional naming, atomic commits with conventional commit messages, interactive rebase, squash merges, PR body generation from commit history, branch cleanup, and git worktree patterns. Use when user asks to create a branch, commit…
git-workflow
Follow this team's Git conventions for branching, commit messages, and pull requests.
github-ops
Fast GitHub operations via the gh CLI. Use when the user mentions GitHub issues, PRs, repos, actions, releases, creating or triaging issues, opening or reviewing pull requests, managing branches, inspecting repo state, or checking CI. Works on any repo the operator's gh CLI is authenticated against.
commit-pr
Squash the branch into one commit and open or update its pull request (creates a new branch first if on main/master).