Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add KnowledgeXLab/skill-git/plugin install skill-gitWrote 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/knowledgexlab/skill-git/check)<a href="https://agentmods.dev/commands/knowledgexlab/skill-git/check"><img src="https://agentmods.dev/badge/commands/knowledgexlab/skill-git/check/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/knowledgexlab/skill-git/check"><img src="https://agentmods.dev/badge/commands/knowledgexlab/skill-git/check.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.00039 | $0.04343 |
| Opus 5.5 | $0.00016 | $0.01737 |
| Sonnet 5.5 | $0.00008 | $0.00869 |
| Haiku 4.5 | $0.00004 | $0.00434 |
Grade A, and why
skill-git:check 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 2mo 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 — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are executing /skill-git:check. Follow the steps below precisely.
Task Tracking
You MUST create a task for each item below and update each task's status as you progress (pending → in_progress → completed):
- Parse arguments and resolve skill — extract skill name, find the file across all known paths
- Resolve agent configuration — determine agent and locate config files
- Read skill and config files — load SKILL.md and agent config files
- Extract and cache rules — run rule extraction (or load from cache) for skill and configs
- Run checks — internal consistency, project config conflicts, global config conflicts, security scan
- Output report — format and display the full check report
- Interactive resolution — work through each fixable conflict if the user chooses to fix (conditional)
- Confirm and write changes — display pending change summary, wait for confirmation, apply file edits to skill and config files (conditional)
Prelude
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/sg-prelude.sh" $ARGUMENTS --agent-only
If STATUS is ok: use AGENT and GLOBAL_BASE from prelude output in Step 2.
If STATUS is not_detected (unknown agent): proceed to Step 2's custom agent lookup path.
If STATUS is error: display REASON and stop.
Step 1: Parse Arguments
The user's input after the command name is: $ARGUMENTS
Extract:
skill_name: the first positional argument (required). Two supported formats:<skill-name>— search across all known skill paths<plugin-name>:<skill-name>— search only within the specified plugin's skills directory
agent: the value after-aflag (optional). Defaults to auto-detect if not provided.
Agent name as skill_name: If the first positional token exactly matches a known agent name (claude, gemini, codex, openclaw) and no -a flag was given, the user likely meant -a <agent> rather than a skill named after the agent. Silently treat it as the agent specifier: re-run the prelude result with that agent (read ~/.skill-git/config.json), set skill_name to empty, and continue to the missing-skill_name error below which will show the usage message.
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.
- 2mo ago First seen · 454 lines · 0 tokens per session scan A 62ff421fa441
skill-git:check is a command published in the GitHub repository KnowledgeXLab/skill-git (42 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 4,343 once invoked, about $0.0002 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 commands, from other repositories
learn
Force claude-smart to extract learnings from this session now.
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
init
Install the formatters this repository needs, with every command visible before it runs.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
check-dev
Type-check a Z specification with fuzz.