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.
git clone --depth 1 https://github.com/fatihkan/badiWrote 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/commands/fatihkan/badi/conv-commit)<a href="https://agentmods.dev/commands/fatihkan/badi/conv-commit"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/conv-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.00000 | $0.00410 |
| Opus 5 | $0.00000 | $0.00205 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
conv-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 today.
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.
What it actually says
Conventional commit helper command. Reads staged files, suggests type/scope/message, and validates.
Required Tools
- Bash (badi commit command invocation)
- git
Procedure
Step 1: Read the Staged Changes
git diff --cached --stat
git diff --cached | head -100
Step 2: Type Selection
By the nature of the change:
- feat: A new user-facing feature
- fix: An existing bug fixed
- refactor: Behavior unchanged, restructuring (rename, extract)
- perf: A measured performance improvement
- docs: Markdown/comment-only changes
- test: Test files only
- chore: Maintenance, config, dependencies
- ci:
.github/workflowsetc. - build: Build system (webpack, tsconfig, etc.)
Step 3: Pick a Scope (optional)
The affected area: auth, api, ui, db, config, a module name, etc.
Step 4: Write the Short Message
Rules:
- Imperative mood, start lowercase
- No trailing period
- < 100 characters (< 70 preferred)
- WHY > WHAT (the commit history must stay readable)
Step 5: Check + Commit with the Badi CLI
# Guidance only
badi commit
# Conventional-format validation + commit
badi commit --message "feat(auth): add JWT refresh tokens"
# Lint check on the last commit
badi commit --check
Step 6: Body and Footer (optional)
For complex changes:
feat(auth): add JWT refresh tokens
1h + refresh pattern instead of a 15-minute expiry.
Offline support for mobile clients.
Closes #123
BREAKING CHANGE: use tokens.access instead of access_token
Example
/conv-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.
- today First seen · 70 lines · 0 tokens per session scan A cfff04763647
conv-commit is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 410 tokens. 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-06.
Other commands, from other repositories
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
catchup
Restore context after /clear by summarizing recent work and project state.
commit
Generate a conventional commit message for staged changes.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
release-notes
Generate release notes in multiple formats from git commits.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.