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 edenismine/expert-factory --skill git-disciplinegit clone --depth 1 https://github.com/edenismine/expert-factoryWrote 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/edenismine/expert-factory/git-discipline)<a href="https://agentmods.dev/skills/edenismine/expert-factory/git-discipline"><img src="https://agentmods.dev/badge/skills/edenismine/expert-factory/git-discipline/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/edenismine/expert-factory/git-discipline"><img src="https://agentmods.dev/badge/skills/edenismine/expert-factory/git-discipline.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.00071 | $0.01719 |
| Opus 5.5 | $0.00028 | $0.00688 |
| Sonnet 5.5 | $0.00014 | $0.00344 |
| Haiku 4.5 | $0.00007 | $0.00172 |
Grade A, and why
git-discipline 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.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git discipline
Three non-negotiables. They apply to every change, including one-line fixes.
- Conventional Commits — every message follows the spec.
- Atomic commits — one logical change per commit, each independently valid.
- Linear history — work on a feature branch, rebase onto the default branch
when behind, integrate with
git merge --ff-only. No merge commits on the default branch, ever.
The default branch
Everything below refers to the repo's default branch — never a hardcoded name.
It may be main, master, trunk, develop, or anything else, and a
long-lived integration branch (develop) may or may not be the same ref. Detect
it; do not assume:
DEFAULT="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||')"
[ -n "$DEFAULT" ] || DEFAULT="$(git rev-parse --abbrev-ref HEAD)"
Capture into a variable and test it; symbolic-ref ... | sed || fallback silently
yields an empty string, because the pipe's exit status is sed's success, not
symbolic-ref's failure.
Notes on the fallback chain:
refs/remotes/origin/HEADis authoritative but is only set bygit clone, so it is often missing in a repo created withgit init. Refresh it withgit remote set-head origin --auto.gh repo view --json defaultBranchRef -q .defaultBranchRef.nameis authoritative for GitHub remotes.init.defaultBranchdescribes what new repos get, not what this repo uses. Do not rely on it.- With no remote, the currently checked-out branch is the best available answer.
If the repo distinguishes a release branch from an integration branch, feature work targets the integration branch; ask which it is rather than guessing.
Below, <default> means that detected name.
1. Conventional Commits
<type>(<optional scope>): <description>
<optional body>
<optional footer>
| Type | Use for |
|---|---|
feat |
new capability |
fix |
bug fix |
docs |
documentation only |
refactor |
restructuring with no behavior change |
perf |
performance |
test |
tests only |
build |
build system, dependencies, Docker |
ci |
CI config |
chore |
maintenance that fits nothing above |
revert |
reverts a previous commit |
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.
- 2mo ago First seen · 183 lines · 71 tokens per session scan A a90bf0340dfa
git-discipline is a skill published in the GitHub repository edenismine/expert-factory (0 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 1,719 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-31.
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 8. 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.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
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…