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 skills add leifericf/agentic-sdk --skill write-commitgit clone --depth 1 https://github.com/leifericf/agentic-sdkWrote 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/leifericf/agentic-sdk/write-commit)<a href="https://agentmods.dev/skills/leifericf/agentic-sdk/write-commit"><img src="https://agentmods.dev/badge/skills/leifericf/agentic-sdk/write-commit.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.00040 | $0.02363 |
| Opus 5 | $0.00020 | $0.01182 |
| Sonnet 5 | $0.00008 | $0.00473 |
| Haiku 4.5 | $0.00004 | $0.00236 |
Grade A, and why
write-commit 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 4d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
write-commit
Invoke before any commit. The project uses jj (Jujutsu) as the VCS, colocated with git for remote compatibility. jj owns the change model; never commit with raw git.
For the prose craft the subject rides on (active voice, concrete over general, no AI tells), invoke write-prose first. This skill owns the form: the jj workflow, the single-line category-first subject, the categories, the pre-flight check.
jj, not git
The repo has both .git/ and .jj/. jj is the source of truth for the
working change; git is the wire format for the remote.
Use:
jj st(status),jj log --limit N(history),jj diff -r @(the current change).jj describe -m "..."to set the message on the current change.jj newfor a fresh empty change on top;jj squashto fold into the parent;jj unsquashto split it back out.jj rebase -r <rev> -d <dest>to rebase onto another change.jj git pushto push (notgit push).
Do not use:
git commit(bypasses jj's change model). Usejj describethenjj new.git add/git rm(jj auto-tracks working-copy mutations; no staging step).git stash(no jj analogue). Usejj newto start a fresh change; the current one is preserved.git rebase(use jj's, which understands colocation).git am/git apply(usejj squashor rebase to move work).
If a git command seems necessary, stop and re-read: jj has an equivalent for every common git operation.
Bookmarks mark, they do not develop
Work is a linear stack of commits on the current tip. @ is the
working-copy commit; describe it, then jj new to advance. There are no
development branches. The protected main bookmark trails the tip and
advances to the latest landed commit only at land time, by the
maintainer. Never base work on main: forking off main when main lags the
tip forks history. A bookmark per major deliverable is named in plain
words for what shipped, placed on the last landed commit with @
already advanced. A bookmark never doubles as a dev branch.
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.
- 4d ago First seen · 210 lines · 40 tokens per session scan A 22f23b787cca
write-commit is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 2,363 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…