Borrowing it
Nothing to install: this file belongs to DevelopmentAgentSDD/MCP-JiraCloud. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DevelopmentAgentSDD/MCP-JiraCloud/main/.opencode/skills/git-flow/SKILL.mdgit clone --depth 1 https://github.com/DevelopmentAgentSDD/MCP-JiraCloudWrote 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/developmentagentsdd/mcp-jiracloud/git-flow)<a href="https://agentmods.dev/skills/developmentagentsdd/mcp-jiracloud/git-flow"><img src="https://agentmods.dev/badge/skills/developmentagentsdd/mcp-jiracloud/git-flow/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/developmentagentsdd/mcp-jiracloud/git-flow"><img src="https://agentmods.dev/badge/skills/developmentagentsdd/mcp-jiracloud/git-flow.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.00050 | $0.00509 |
| Opus 5.5 | $0.00020 | $0.00204 |
| Sonnet 5.5 | $0.00010 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
git-flow 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.
What it actually says
Git Flow para Microservicios .NET Core
Ramas principales
main # Produccion (solo mergea desde release/* y hotfix/*)
develop # Integracion continua (mergea desde feature/* y release/*)
Ramas de soporte
| Rama | Proposito | Nomenclatura | Se crea desde | Mergea a |
|---|---|---|---|---|
feature/* |
Nueva funcionalidad | feature/F001-crear-pedido |
develop |
develop |
release/* |
Preparar release | release/1.0.0 |
develop |
main + develop |
hotfix/* |
Correccion urgente | hotfix/1.0.1-corregir-pago |
main |
main + develop |
Flujo de feature con arneses
Cuando leader invoca features start F001:
git checkout develop
git pull origin develop
git checkout -b feature/F001-crear-pedido
El desarrollo se realiza en esta rama. Al completar la feature:
git checkout develop
git merge --no-ff feature/F001-crear-pedido
git push origin develop
git branch -d feature/F001-crear-pedido
Convenciones de commit
feat: agregar creacion de pedidos con validacion de stock
fix: corregir calculo de total con descuentos
refactor: extraer OrderCalculator a servicio de dominio
test: agregar pruebas de integracion para OrderRepository
docs: actualizar architecture.md con ADR-003
Reglas
mainnunca recibe commits directosdevelopnunca recibe commits directos (solo merges)- Cada feature tiene su propia rama
feature/{id}-{slug} - Usar
--no-ffal mergear features para preservar historial - Eliminar la rama feature despues del merge exitoso
- Antes de mergear a
develop, ejecutardotnet testydotnet format --verify-no-changes
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 · 60 lines · 0 tokens per session scan A 8987778e1f6b
git-flow is a skill published in the GitHub repository DevelopmentAgentSDD/MCP-JiraCloud (0 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 509 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-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.