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/xllm-ai/xllm/git-workflownpx skills add xLLM-AI/xllm --skill git-workflowgit clone --depth 1 https://github.com/xLLM-AI/xllmWrote 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/xllm-ai/xllm/git-workflow)<a href="https://agentmods.dev/skills/xllm-ai/xllm/git-workflow"><img src="https://agentmods.dev/badge/skills/xllm-ai/xllm/git-workflow.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.00052 | $0.00709 |
| Opus 5 | $0.00026 | $0.00354 |
| Sonnet 5 | $0.00010 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
git-workflow 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Use xLLM repo reality, not generic Git habits.
Reference Map
Load only the file that matches the user's immediate Git task.
| File | What it is for | When to load it |
|---|---|---|
references/source-of-truth.md |
Repo-specific source priority and canonical files to consult | Load first when repo docs, local state, and user wording may disagree |
references/branch-naming.md |
Branch naming patterns and default branch conventions | Load when the user asks how to name a branch or which branch to branch from |
references/development-flow.md |
Day-to-day fork, sync, branch, validate, and push flow | Load when the user asks for normal development steps from local change to push |
references/pr-review.md |
PR targeting, PR scope, and review expectations | Load when the task is about opening a PR, choosing the target branch, or deciding who should review |
references/release-layout.md |
Release branch and tag shapes used by xLLM | Load when the task mentions release branches, release tags, or patch version naming |
references/backport-flow.md |
Preferred backport and hotfix flow for released lines | Load when the task mentions cherry-picks, hotfixes, or fixing an already released branch |
references/commit-format.md |
Commit title/body conventions and xLLM-style examples | Load when the user asks for a commit message, commit style guidance, or message cleanup |
Workflow
- Decide which subtask the user actually needs.
- Read
references/source-of-truth.mdwhen you need repo-specific confirmation. - Then load only the most relevant task file from the table above.
- For commit message drafting, run
bash scripts/collect_git_context.sh [--staged|--all|--unstaged]before writing the final message. - Draft commit messages from the actual diff, not from filenames alone.
- If one diff mixes unrelated concerns, recommend splitting the commit instead of forcing one vague summary.
- Default PR targets to
mainunless the task is clearly a release or backport flow. - For released lines, prefer landing on
mainfirst and then backporting unless the user explicitly wants a direct hotfix flow.
What ships with it
8 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 First seen · 50 lines · 52 tokens per session scan A b521f2e5d9b3
git-workflow is a skill published in the GitHub repository xLLM-AI/xllm (1,556 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 709 once invoked, about $0.0003 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 skills, from other repositories
qa-testing
Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…
onboard-model
Onboard or periodically reverify and benchmark a Hugging Face model on an exact target GPU platform. Use when asked to add a model recipe, refresh a maintained recipe on a supplied GPU server, benchmark serving, create reproducible experiments and a durable results report, fully qualify and tune the model's Emmy…
reproduce-article-benchmarks
Use this skill when the user asks to re-run an article's benchmarks, reproduce blog post numbers, validate that an article URL still holds, check whether the latest code still performs like a published post, or otherwise compare re-measured Emmy results with published results. It fetches the article, finds its…
tune-kernels
Tune Emmy kernels for a Hugging Face model, traced IR, or golden YAML. Use when asked to tune a model or golden set, seed MCTS with model-proposed knob configurations, compare hybrid proposals against MCTS-only search, diagnose slow or failing kernels, refresh per-GPU goldens, or produce a per-kernel tuning findings…
discover-models
Use this skill when the user asks what new models to try or benchmark, wants newly released open models discovered, wants trending models mapped to suitable GPU hardware, or wants the maintained recipe set refreshed. It produces a ranked shortlist or lifecycle selection ready for the onboard-model skill, using keyless…
run-experiment
Run or rerun Emmy experiment recipes, including requests to adjust an experiment harness before running it, then preserve per-platform compressed raw results with system-only YAML experiment records and a thoughtful cumulative RESULTS.md interpretation. Use for requests such as "run this experiment", "benchmark this…