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 skills add JotJunior/cstk --skill jira-convertgit clone --depth 1 https://github.com/JotJunior/cstkWrote 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/jotjunior/cstk/jira-convert)<a href="https://agentmods.dev/skills/jotjunior/cstk/jira-convert"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/jira-convert/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/jotjunior/cstk/jira-convert"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/jira-convert.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.00127 | $0.06017 |
| Opus 5.5 | $0.00051 | $0.02407 |
| Sonnet 5.5 | $0.00025 | $0.01203 |
| Haiku 4.5 | $0.00013 | $0.00602 |
Grade A, and why
jira-convert 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.
How it starts
The opening of the file, as written. The whole thing — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Conversao feature -> Jira (jira-convert)
Cria, no Jira, o Epic + Tasks + Sub-tasks correspondentes ao backlog local
de UMA feature (docs/specs/<feature>/spec.md + tasks.md), gravando a
associacao local<->Jira em docs/specs/<feature>/jira-map.tsv. Reexecucao
e sempre segura: so cria o que ainda nao esta mapeado (US1 cenario 2).
Ref: docs/specs/cstk-jira/spec.md US1, FR-001/FR-003/FR-013/FR-014;
plan.md Fluxo 2 "Convert"; data-model.md Entity LocalWorkItem/
SyncMapping; checklists/api.md CHK012/CHK013; checklists/security.md
CHK005; checklists/ux.md CHK013; contracts/rovo-mcp.md;
contracts/jira-rest.md R1.
Pre-requisitos
jira-config.sh validateexit 0 (setup ja concluido — se nao, rode/jira-setupprimeiro).- Feature com
docs/specs/<feature>/tasks.mdexistente (spec.mde OPCIONAL — sem ele, o titulo do Epic cai para o proprio short-name da feature,jira-tasks.shcomentario 2.2.5). - Scripts do plugin no mesmo diretorio:
jira-config.sh,jira-io.sh,jira-tasks.sh,jira-map.sh,jira-title.sh,jira-sync.sh.
Proximos passos
/jira-sync statuspara ver o resultado (contagem por status, conflitos, orfaos) e disparar a sincronizacao continua de status (US3) daqui em diante.- Rodar esta skill de novo a qualquer momento que
tasks.mdganhar itens novos — cria SOMENTE os itens novos (US1 cenario 2).
FLUXO DE EXECUCAO (ordem FIXA)
1. PRE-CHECAGENS 4 checagens, SEMPRE, antes de QUALQUER escrita —
identicas nos dois caminhos (ver ETAPA 1 e Gotcha
"Por que a credencial REST importa mesmo no MCP")
|
2. DETECCAO DE CAMINHO Tools Rovo (sufixo `__createJiraIssue` etc.)
visiveis nesta sessao? -> MCP; senao -> REST
|
3a. CAMINHO REST Delega inteiro a `jira-sync.sh convert --feature F`
| (ETAPA 2a)
3b. CAMINHO MCP Loop item a item: jira-tasks.sh items -> skip se
| ja mapeado -> jira-title.sh compose -> tool MCP
| createJiraIssue -> jira-map.sh put -> SyncMarker
| inicial via jira-io.sh REST (ETAPA 2b passos 1-7b);
| ao final do loop, jira-sync.sh convert 1x para
| fechar paridade de itens ja mapeados (passo 8)
|
4. RELATORIO FINAL Quantos criados / quantos ja existiam (pulados)
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.
- 15d ago Changed · -1 tokens per session 34277ed73c23
- 17d ago First seen · 377 lines · 128 tokens per session scan A c0b2f028fe1d
jira-convert is a skill published in the GitHub repository JotJunior/cstk (24 stars, last pushed 6d ago), licensed MIT. It adds 127 tokens to every session and 6,017 once invoked, about $0.0005 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.
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.
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.
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.
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.
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.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.