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 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/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/skills/musoyangrigor/gitx-skill/gitx"><img src="https://agentmods.dev/badge/skills/musoyangrigor/gitx-skill/gitx.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 178 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00087 | $0.03216 |
| Opus 5.5 | $0.00035 | $0.01286 |
| Sonnet 5.5 | $0.00017 | $0.00643 |
| Haiku 4.5 | $0.00009 | $0.00322 |
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 3d 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.
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.
Commands and dispatch
Match natural-language requests to the commands below. Route “check my changes” or “show git status” to Status when the user wants a read-only summary; route “run tests before committing” to Checks. Use Doctor for Git workflow diagnosis and Plan for a commit preview. Read supporting references only when their workflow or loading condition applies.
Route gitx issue by argument shape, not by the intent implied by its wording. An argument containing only an issue number, such as 123 or #123, selects the existing-issue implementation workflow. Treat every other non-empty argument as a description for a new GitHub issue, even when it contains words such as “fix,” “update,” or “resolve.” With no argument, ask for the issue description. Never implement a problem supplied as a non-numeric gitx issue description.
gitx issue <description> explicitly requests publication to GitHub. Repository-local tracker conventions do not redirect this command to local files; follow the GitHub issue creation workflow, including its failure handling.
For gitx ship [base], the optional argument is the PR's destination branch, never the name of a new feature branch. For example, gitx ship dev targets dev. Dispatch to Ship, not directly to Branch or Pull requests.
| Command | Action |
|---|---|
gitx |
Create a smart commit. |
gitx setup |
Preview and save project preferences in the repository's .gitx.json. |
gitx body |
Create a smart commit with a useful commit body. |
gitx branch [name] |
Create and switch to a branch. |
gitx branch check |
Create a default branch, run checks, then create a smart commit. |
gitx pull |
Safely pull updates for the current branch. |
gitx push |
Push the current branch to origin. |
gitx pr [base] |
Create a GitHub pull request into the supplied, configured, or default base branch. |
gitx ship [base] |
Create a feature branch when needed, run checks, commit, push, and open a PR into the supplied, configured, or default base branch. |
gitx issue <description> |
Create a GitHub issue with a generated title and body. |
gitx issue <number> |
Fix the GitHub issue with that number. |
gitx resolve |
Resolve an in-progress merge or rebase conflict. |
gitx check |
Run relevant checks, then create a smart commit. |
gitx status |
Show Git status and changed-file summary; make no changes. |
gitx doctor [problem] |
Diagnose repository problems and suggest next steps; make no changes. |
gitx tree |
Show a compact Git history tree and repository context; make no changes. |
gitx scan |
Scan changes and history for exposed secrets and sensitive files; make no changes. |
gitx plan |
Preview the proposed commit groups and messages; make no changes. |
gitx type <type> |
Create a smart commit using the given Conventional Commit type. |
gitx scope <scope> |
Create a smart commit using the given scope. |
gitx files <paths> |
Create a smart commit using only the given files. |
gitx amend |
Ask for confirmation, then amend the most recent commit. |
What ships with it
9 files 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.
- 3d ago Changed · +2 lines b08a9a1a1e18
- 14d ago Changed · -71 lines 4c2d980febbc
- 1mo ago Changed · +29 lines · +3 tokens per session 18a03069a430
- 1mo ago First seen · 196 lines · 84 tokens per session scan A 264585e21b99
gitx is a skill published in the GitHub repository musoyangrigor/gitx-skill (97 stars, last pushed 4d ago), licensed MIT. It adds 87 tokens to every session and 3,216 once invoked, about $0.0003 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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.