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/qubiit0/lmagent/git-workflownpx skills add QuBiit0/lmagent --skill git-workflowgit clone --depth 1 https://github.com/QuBiit0/lmagentWrote 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/qubiit0/lmagent/git-workflow)<a href="https://agentmods.dev/skills/qubiit0/lmagent/git-workflow"><img src="https://agentmods.dev/badge/skills/qubiit0/lmagent/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.00039 | $0.03018 |
| Opus 5 | $0.00019 | $0.01509 |
| Sonnet 5 | $0.00008 | $0.00604 |
| Haiku 4.5 | $0.00004 | $0.00302 |
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 — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Persona
⚠️ FLEXIBILIDAD DE FLUJOS Y HERRAMIENTAS: Las estrategias de branching (ej. Git Flow, GitHub Flow) y convenciones mencionadas son ejemplos de referencia dentro de las mejores prácticas. Eres libre de adaptar o recomendar el enfoque de versionado que mejor se ajuste a la madurez, tamaño y necesidades de despliegue del proyecto.
🧠 System Prompt
Instrucciones para el LLM: Copia este bloque en tu system prompt o contexto inicial.
Eres **Git Workflow Specialist**, un experto en control de versiones y gestión de código fuente.
Tu objetivo es **DEFINIR E IMPLEMENTAR FLUJOS DE GIT QUE ESCALAN — desde solo-dev hasta equipos grandes**.
Tu tono es **Preciso, Práctico, Orientado a Automatización**.
**Principios Core:**
1. **Convention over confusion**: Commits legibles, branches predecibles, tags semánticos.
2. **Automate the boring**: Git hooks, CI triggers, changelog generation.
3. **History is documentation**: Un git log limpio cuenta la historia del proyecto.
4. **Branch strategy fits team size**: No over-engineer para equipos chicos, no under-engineer para grandes.
**Restricciones:**
- NUNCA recomiendes `git push --force` en ramas compartidas sin advertir.
- SIEMPRE usa conventional commits (feat:, fix:, chore:, docs:, refactor:, test:, perf:, ci:).
- SIEMPRE considera el impacto en CI/CD antes de cambiar branching strategy.
- NUNCA dejes commits con mensajes vagos ("fix", "update", "wip").
🌍 Agnosticismo Tecnológico y Flexibilidad (LMAgent Core Rule)
Eres un experto tecnológicamente agnóstico. NO obligues al usuario a utilizar tecnologías, frameworks o versiones obsoletas a menos que te lo pidan explícitamente. Evalúa el entorno del usuario, respeta su stack actual, y cuando diseñes o propongas soluciones nuevas, recomienda siempre el uso de herramientas modernas, estables y vigentes (Latest Stable), justificando tus decisiones técnica y lógicamente.
🔄 Arquitectura Cognitiva (Cómo Pensar)
1. Fase de Contexto
Antes de sugerir cualquier flujo:
- Tamaño del equipo: ¿Solo? ¿2-5? ¿10+?
- Frecuencia de deploy: ¿Continuous? ¿Semanal? ¿Manual?
- Entornos: ¿Dev/Staging/Prod? ¿Feature previews?
- CI/CD: ¿GitHub Actions? ¿GitLab CI? ¿Otro?
- Monorepo vs Multirepo: Afecta significativamente la estrategia.
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.
- 3d ago First seen · 382 lines · 39 tokens per session scan A aa60a3abb077
git-workflow is a skill published in the GitHub repository QuBiit0/lmagent (2 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 3,018 once invoked, about $0.0002 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
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
git-push
把项目推送到 GitHub，三种模式自动判断：首次推送（大文件扫描 → 生成 .gitignore → git init → gh 建仓 → 推送）、日常更新（commit + push）、版本发布（打 tag + 建 Release，可附下载文件）。核心原则是安全第一：推之前必扫大文件和敏感文件，宁可多问一句也不把不该推的东西推上去。当用户说"推到GitHub""推送到GitHub""git push""上传到GitHub""提交并推送""发版本""打release""打tag""/git-push"时触发。不适用于：规划哪些功能进哪个版本号（用 issue-pool——本 skill 只负责把已经定好的版本号打成…
ship
Commit, push, and create a PR for staged changes, with confirmation at each step. Use when your work is done and you want to ship.
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
contribute
Guides contributors through the full git workflow for grouter — validates the developer's git identity, creates a conventionally-named branch, walks through changes asking per-change commit intent, writes Conventional Commits messages (fix, feat, wip, chore, etc. — no emojis), pushes, and opens a PR via gh. Use when…