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/branch)<a href="https://agentmods.dev/commands/bityoungjae/marketplace/branch"><img src="https://agentmods.dev/badge/commands/bityoungjae/marketplace/branch/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/branch"><img src="https://agentmods.dev/badge/commands/bityoungjae/marketplace/branch.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.00009 | $0.01156 |
| Opus 5 | $0.00005 | $0.00578 |
| Sonnet 5 | $0.00002 | $0.00231 |
| Haiku 4.5 | $0.00001 | $0.00116 |
Grade A, and why
branch 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gitkkal branch
Analyzes changes and generates an appropriate branch name, then creates the branch.
Critical Rules
- NEVER create branches with non-English names
- NEVER use special characters except hyphens
- Branch names MUST be lowercase kebab-case
- Maximum 50 characters for branch name
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. Analyze Current State
Run in parallel:
git status --short
git diff # Actual content changes (unstaged)
git diff --cached # Actual content changes (staged)
- No changes → Ask user for branch description directly
- Changes exist → Proceed to semantic analysis
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 (e.g., "renaming SKU to Bundle ID", "adding retry logic")
- Look for patterns: variable renames, API changes, new abstractions, bug fixes
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 · 156 lines · 9 tokens per session scan A fffcf401881a
branch is a command published in the GitHub repository BitYoungjae/marketplace (6 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 1,156 once invoked, about $0.0000 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 commands, from other repositories
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.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.