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/qqabcv520/my-claude-marketplacesWrote 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/qqabcv520/my-claude-marketplaces/commit)<a href="https://agentmods.dev/commands/qqabcv520/my-claude-marketplaces/commit"><img src="https://agentmods.dev/badge/commands/qqabcv520/my-claude-marketplaces/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.00009 | $0.00741 |
| Opus 5 | $0.00005 | $0.00370 |
| Sonnet 5 | $0.00002 | $0.00148 |
| Haiku 4.5 | $0.00001 | $0.00074 |
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 7d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Current git status: !
git status - Current git diff (staged and unstaged changes): !
git diff HEAD - Current branch: !
git branch --show-current - Recent commits: !
git log --oneline -10
Your task
Based on the above context, create a git commit following Conventional Commits specification.
Command Options
--no-verify: Pass--no-verifyflag to git commit--style=simple|full:simple(default): Concise single-line commit messagefull: Detailed commit message with body and footer
--type=<type>: Override automatic type detection
Workflow
- Check staged files: Run
git statusto see what's staged - Auto-stage if needed: If nothing is staged, run
git addfor all modified/new files - Analyze changes: Run
git diff --cachedto understand staged changes - Detect split need: If changes span multiple unrelated concerns, suggest splitting into atomic commits
- Generate commit message: Follow Conventional Commits format based on style setting
- Execute commit: Run
git commitwith the generated message
Conventional Commits Format
Simple Style (Default)
<type>[optional scope]: <description>
Example: feat(auth): add JWT token validation
Full Style
<type>[optional scope]: <description>
<body>
<footer>
Commit Types
| Type | When to Use |
|---|---|
feat |
Adding new functionality |
fix |
Fixing a bug |
docs |
Documentation only changes |
style |
Formatting, whitespace, etc |
refactor |
Neither fixes bug nor adds feature |
perf |
Performance improvements |
test |
Adding or updating tests |
chore |
Maintenance, build process, tools |
ci |
CI/CD configuration changes |
build |
Build system changes |
revert |
Reverting previous commit |
Rules
- Write in present tense, imperative mood ("add" not "added")
- Keep subject line under 72 characters
- Capitalize first letter of description
- No period at end of subject line
- Use body to explain what and why (not how)
- Pass commit message via HEREDOC for proper formatting:
git commit -m "$(cat <<'EOF' type(scope): description Body text here. EOF )"
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.
- 7d ago First seen · 104 lines · 9 tokens per session scan A 6b939ef67484
commit is a command published in the GitHub repository qqabcv520/my-claude-marketplaces (2 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 741 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
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
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.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
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.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.