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/BitYoungjae/marketplaceWrote 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/bityoungjae/marketplace/commit)<a href="https://agentmods.dev/commands/bityoungjae/marketplace/commit"><img src="https://agentmods.dev/badge/commands/bityoungjae/marketplace/commit/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/commands/bityoungjae/marketplace/commit"><img src="https://agentmods.dev/badge/commands/bityoungjae/marketplace/commit.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.00010 | $0.01426 |
| Opus 5.5 | $0.00004 | $0.00570 |
| Sonnet 5.5 | $0.00002 | $0.00285 |
| Haiku 4.5 | $0.00001 | $0.00143 |
Grade A, and why
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 1mo 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gitkkal commit
Analyzes changes and creates commits following the configured style.
Critical Rules
- NEVER include
Co-Authored-Bylines in commit messages - NEVER use
git commit --amend— always create NEW commits - NEVER use
git add -Aorgit add .— stage files individually - NEVER commit sensitive files (.env, credentials, API keys)
- ALWAYS use HEREDOC for commit messages to ensure proper formatting
Workflow
1. Load Configuration
git rev-parse --show-toplevel # Find project root
Read {project_root}/.gitkkal/config.json. If not exists, use defaults and display once:
"Using default settings. Run /gitkkal:init to customize."
2. Gather Change Information
Run in parallel:
git status --short # All file states (NEVER use -uall flag)
git diff --cached # Staged changes (actual content)
git diff # Unstaged changes (actual content)
git log --oneline -5 # Recent commit style reference
Commit candidates (analyze all together):
- Staged changes (index)
- Unstaged changes (modified tracked files)
- Untracked files (new files)
3. Understand Semantic Intent
Focus on the "why" rather than the "what":
- Read actual diff content, not just file statistics
- Identify the semantic meaning of changes
- Determine if changes represent: new feature, enhancement to existing feature, bug fix, refactoring, etc.
- Ensure verb choice reflects intent: "add" = wholly new, "update" = enhancement, "fix" = bug fix
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.
- 1mo ago First seen · 181 lines · 10 tokens per session scan A f3ef4edd0555
commit is a command published in the GitHub repository BitYoungjae/marketplace (6 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 1,426 once invoked, about $0.0000 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 commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.