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/developmentagentsdd/mcp-jiracloud/git-flownpx skills add DevelopmentAgentSDD/MCP-JiraCloud --skill git-flowgit clone --depth 1 https://github.com/DevelopmentAgentSDD/MCP-JiraCloudWhat 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.00050 | $0.00509 |
| Opus 5 | $0.00025 | $0.00254 |
| Sonnet 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 yesterday.
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.
- yesterday 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 2mo ago), licensed MIT. It adds 50 tokens to every session and 509 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.