jira-sync

jira-sync is a skill for Claude Code from JotJunior/cstk. It costs 156 tokens per session (4,968 once invoked), scanned A, original, MIT.

A control panel for synchronizing local work items with Jira, a service for tracking issues and project tasks. It shows queued updates, conflicts, and Jira cards that no longer have a local match, then guides a person through the required decisions.

In plain words
What is it for?
It helps inspect the synchronization queue, review conflict details, resolve status differences, and reconnect orphaned Jira cards while background synchronization continues.
Why use it?
It makes synchronization problems visible instead of silently leaving local and Jira status out of step. Human approval is kept for choices such as keeping Jira's version, overwriting it, ignoring the conflict, or reconnecting an unmatched card.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the cstk-jira plugin — 3 skills shipped together

Good fit It helps inspect the synchronization queue, review conflict details, resolve status differences, and reconnect orphaned Jira cards while background synchronization continues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jotjunior/cstk/jira-sync
Install

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.

Any agent
npx skills add JotJunior/cstk --skill jira-sync
Clone the repo
git clone --depth 1 https://github.com/JotJunior/cstk

Made for: Claude Code.

Or install cstk-jira, the plugin that ships this one along with the rest of its 3 skills.

Wrote 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.

agentmods badge for jira-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/jotjunior/cstk/jira-sync/github.svg)](https://agentmods.dev/skills/jotjunior/cstk/jira-sync)
Your own site
<a href="https://agentmods.dev/skills/jotjunior/cstk/jira-sync"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/jira-sync/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.

agentmods 80×15 button for jira-sync

Your own site · 80×15
<a href="https://agentmods.dev/skills/jotjunior/cstk/jira-sync"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/jira-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 156 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,968 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00156 $0.04968
Opus 5.5 $0.00062 $0.01987
Sonnet 5.5 $0.00031 $0.00994
Haiku 4.5 $0.00016 $0.00497

Measured 15d ago against content hash 628e99477079, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jira-sync 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 15d 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.

plugins/cstk-jira/skills/jira-sync/SKILL.md · 318 lines

How it starts

The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: Status e resolucao de sincronizacao (jira-sync)

Interface do operador para a sincronizacao AUTONOMA de status entre tarefas locais e cards do Jira (US3): mostra o estado da fila (outbox.tsv), lista conflitos pendentes (ConflictRecord) e cards orfaos, e conduz a resolucao humana de cada um — a sincronizacao continua (drain do outbox durante agente-00c/feature-00c) segue rodando por hook, sem interacao; esta skill e para quando o operador precisa OLHAR e DECIDIR algo.

Ref: docs/specs/cstk-jira/spec.md US3, FR-004/FR-005/FR-011/FR-012/ FR-018; plan.md Fluxo 3 "Sync autonomo"; data-model.md Entity OutboxEvent/ConflictRecord/SyncMapping; checklists/ux.md CHK011/CHK012; checklists/security.md CHK005/SEC-2; contracts/hooks.md; contracts/jira-rest.md R3; contracts/plugin-scripts.md jira-sync.sh/ jira-map.sh.

Pre-requisitos

  • jira-config.sh validate exit 0 (setup ja concluido — se nao, rode /jira-setup primeiro).
  • Feature convertida (docs/specs/<feature>/jira-map.tsv existente — rode /jira-convert primeiro se ainda nao houver mapeamento).
  • Scripts do plugin no mesmo diretorio: jira-config.sh, jira-io.sh, jira-sync.sh, jira-map.sh, jira-conflict-view.sh.

Proximos passos

  • Rode /jira-sync a qualquer momento durante uma execucao agente-00c/ feature-00c longa para conferir se o board reflete o andamento real (US3 cenario 1-3) ou se algo precisa de decisao humana.

FLUXO DE EXECUCAO (ordem FIXA)

1. STATUS              jira-sync.sh status [--feature F] — fila, conflitos
     |                  pendentes, orfaos, auth_failed (ETAPA 1)
     |
2. HA CONFLITO       -> operador escolhe um par (feature, local_key) para
   PENDENTE?             INSPECIONAR -> ETAPA 2 (exibicao rotulada UNTRUSTED
     |                    + jira-sync.sh resolve)
     |
3. HA ORFAO?         -> operador decide religar -> ETAPA 3 (jira-map.sh
     |                    relink) ou deixar como esta (nada acontece,
     |                    FR-012 — card nunca e apagado)
     |
4. auth_failed?      -> ETAPA 4 (diagnostico: rodar /jira-setup de novo)
     |
5. Sincronizacao manual (opcional) -> jira-sync.sh drain --feature F, se
     o operador quiser forcar o drain do outbox fora do ciclo do hook

Read the full file on GitHub · 318 lines

Files

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.

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.

  1. 15d ago Changed · -1 tokens per session 628e99477079
  2. 17d ago First seen · 318 lines · 157 tokens per session scan A a0d369fc17b6

Subscribe to this mod's changes

jira-sync is a skill published in the GitHub repository JotJunior/cstk (24 stars, last pushed 6d ago), licensed MIT. It adds 156 tokens to every session and 4,968 once invoked, about $0.0006 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-09-29.

Related

Other skills, from other repositories

paperclip

Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.

paperclipai/paperclip · 54 tokens

paperclip

Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.

paperclipai/paperclip · 43 tokens

paperclip-board

Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.

paperclipai/paperclip · 47 tokens

paperclip-distill

Use when an operation issue is a Paperclip cursor-window, distill, or backfill. Turn source-bundled Paperclip activity into wiki-insightful project standups, durable project pages, decisions, and history without asset dereferencing.

paperclipai/paperclip · 54 tokens

summarize-status

Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.

paperclipai/paperclip · 0 tokens

paperclip-task-bridge

Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.

paperclipai/paperclip · 27 tokens