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 agentmods add skills/musoyangrigor/gitx-skill/gitxnpx skills add musoyangrigor/gitx-skill --skill gitxgit clone --depth 1 https://github.com/musoyangrigor/gitx-skillWrote 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/musoyangrigor/gitx-skill/gitx)<a href="https://agentmods.dev/skills/musoyangrigor/gitx-skill/gitx"><img src="https://agentmods.dev/badge/skills/musoyangrigor/gitx-skill/gitx.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 | $0.00084 | $0.03756 |
| Opus 5 | $0.00042 | $0.01878 |
| Sonnet 5 | $0.00017 | $0.00751 |
| Haiku 4.5 | $0.00008 | $0.00376 |
Grade A, and why
gitx 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 5d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitX
Default action
On a bare invocation—$gitx, gitx, or a skill-UI invocation with no extra command—immediately execute the Smart commit workflow. Make the first action a repository inspection with Git status and the relevant diff. After inspecting, create the appropriate commit or report that there is nothing to commit.
Treat a bare invocation as an action, never as a help request. Do not announce that GitX was loaded, list commands or examples, ask which command to run, or wait for more instructions. Show the command list only when the user explicitly asks for help or available commands.
Overview and when to use GitX
Use GitX as one Git workflow skill for AI coding agents, from messy working-tree changes to clean commits, branches, checks, pushes, pull requests, issues, secret scanning, and conflict resolution. Use it to inspect changed files, group related work into logical commits, generate Conventional Commit messages, run relevant project checks, create safe branches, pull and push safely, create GitHub pull requests, create or implement GitHub issues, detect exposed credentials, resolve merge or rebase conflicts, understand repository state, and preview a commit plan before changing anything.
Use GitX when a user asks to:
- Commit changes cleanly: “commit my changes,” “make a clean commit,” “generate a conventional commit,” “split these changes into commits,” or “plan my commits.”
- Work with branches: “create a branch” or “create a feature branch.”
- Inspect or validate repository state: use
gitx statusfor “check my changes” or “show git status” when the user wants a read-only summary,gitx treefor “show git history,”gitx scanfor exposed secrets or sensitive files, andgitx checkfor “run tests before committing” or another check-and-commit request. - Publish work: “pull latest changes,” “push my branch,” “create a PR,” or “open a GitHub pull request.”
- Work from GitHub tasks or integration problems: “create a GitHub issue,” “fix issue #123,” “resolve merge conflicts,” or “resolve rebase conflicts.”
- Clean up AI-generated changes, organize unrelated file changes, prepare code for review, or improve work produced by Claude Code, OpenAI Codex, Cursor, or another coding agent.
What ships with it
1 file 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.
- 5d ago First seen · 196 lines · 84 tokens per session scan A 264585e21b99
gitx is a skill published in the GitHub repository musoyangrigor/gitx-skill (62 stars, last pushed 18d ago), licensed MIT. It adds 84 tokens to every session and 3,756 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-30.
Other skills, from other repositories
git-commit
Generate well-formatted git commit messages following conventional commit standards.
test-repo
Use this skill to test strategy changes against a fresh test repository. Invoke when the user asks to "test against a test repo", "validate the changes", or wants to verify session hooks, commits, and checkpoint creation work correctly.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
commit
Commit current changes with a clear, descriptive message.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…