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 lossless-group/lossless-agent-skills --skill git-conventionsgit clone --depth 1 https://github.com/lossless-group/lossless-agent-skillsWrote 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/lossless-group/lossless-agent-skills/git-conventions)<a href="https://agentmods.dev/skills/lossless-group/lossless-agent-skills/git-conventions"><img src="https://agentmods.dev/badge/skills/lossless-group/lossless-agent-skills/git-conventions/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/lossless-group/lossless-agent-skills/git-conventions"><img src="https://agentmods.dev/badge/skills/lossless-group/lossless-agent-skills/git-conventions.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.00075 | $0.03116 |
| Opus 5 | $0.00037 | $0.01558 |
| Sonnet 5 | $0.00015 | $0.00623 |
| Haiku 4.5 | $0.00007 | $0.00312 |
Grade A, and why
git-conventions 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 9d 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Conventions
The Lossless Group's conventions for git commit messages — making history readable, searchable, and useful for future-you.
Status: Initial scaffold (May 2026) — documenting observed patterns from lossless-monorepo.
When to use this skill
- Writing commit messages (any repo)
- Reviewing commits before push
- Teaching commit conventions to collaborators
- User asks "how should I format this commit?"
- User mentions "commit message", "git conventions", "effort grouping"
Core Patterns
1. Header Syntax
Two accepted patterns:
Pattern A: Single effort grouping
{action}({effort-grouping}): {narrative description}
Pattern B: Multiple effort groupings or chained actions
{action}({effort-1}, {effort-2}): {narrative description}
{action}({effort-1}), {action}({effort-2}): {narrative description}
Examples:
feat(theme-system): Add vibrant mode verification checklist
fix(mode-switcher, theme.css): Vibrant mode now dark-based with neon effects
doc(README), skill(astro-knots): Update vibrant mode guidance
2. Common Action Verbs
| Action | When to use |
|---|---|
feat |
New feature, new capability |
fix |
Bug fix, correction |
doc |
Documentation changes |
refactor |
Code restructure without behavior change |
style |
Formatting, whitespace (no logic change) |
test |
Adding/updating tests |
chore |
Maintenance, deps, tooling |
skill |
Skill file changes (lossless-skills repo) |
changelog |
Changelog entry added/updated |
3. Effort Groupings
What is an effort grouping? The part of the codebase this commit touches — a package, a site, a system, a concern.
Examples:
skill(theme-system)— changes to theme-system skillfeat(reach-edu-hub)— new feature in reach-edu-hub sitefix(mode-switcher, theme.css)— bug fix touching both files/systemsdoc(README, CANDIDATES)— documentation changes in both files
Guideline: Use the most specific grouping that makes sense. If a commit touches multiple unrelated areas, consider splitting into multiple commits.
What ships with it
3 files 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.
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.
- 9d ago First seen · 327 lines · 75 tokens per session scan A 27e1a6be1d76
git-conventions is a skill published in the GitHub repository lossless-group/lossless-agent-skills (4 stars, last pushed 16d ago), licensed MIT. It adds 75 tokens to every session and 3,116 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
github-commander
Structured workflows for GitHub issues, PRs, milestones, and code audits with validation gates and HITL checkpoints. Use when assigned a GitHub issue, reviewing a PR, sprinting through a milestone, updating dependencies, or running code audits. Also use when asked to "triage an issue", "review a PR", or "update deps".…
review-before-commit
Run a behavioral self-check before persisting story results. Verifies diff simplicity, scope adherence, and verifiable completion against enso §10 behavioral principles. Use when a story's implementation is complete and ready to close.
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-quick-batch
Batch several /gsd:quick-shaped tasks together — planned, dispatched, and merged as one run.
commit-with-reflection
A Git workflow that creates a Chinese-language report about debugging mistakes, investigation steps, fixes, and lessons learned, then includes that report in a commit. Git is a system for tracking changes to code.
gsd-pause-work
Create context handoff when pausing work mid-phase.