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-setupgit 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-setup)<a href="https://agentmods.dev/skills/jotjunior/cstk/jira-setup"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/jira-setup/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-setup"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/jira-setup.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.00121 | $0.06502 |
| Opus 5.5 | $0.00048 | $0.02601 |
| Sonnet 5.5 | $0.00024 | $0.01300 |
| Haiku 4.5 | $0.00012 | $0.00650 |
Grade A, and why
jira-setup 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 17d 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 — 467 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Setup guiado do cstk-jira (jira-setup)
Conduz a configuracao inicial (ou reconfiguracao) do plugin cstk-jira
para o projeto-alvo corrente: grava ProjectConfig
(.claude/cstk-jira/config) e orienta a gravacao da Credential local,
descobrindo do Jira real (nunca de memoria) os tipos de issue e os status
do workflow que o operador precisa mapear.
Ref: docs/specs/cstk-jira/spec.md US4/FR-024; plan.md Fluxo 1 "Setup" e
Fluxo 7 "Setup com oferta de projeto"; quickstart.md Cenario 3 e Cenario
11; data-model.md Entity ProjectConfig/Credential; checklists/ux.md
CHK001-CHK006/CHK014/CHK015; checklists/security.md CHK004/CHK005/CHK022
(SEC-7/SEC-9); contracts/jira-rest.md R1/R5/R8/R9/R10/R11/R18;
contracts/rovo-mcp.md.
Pre-requisitos
- Projeto Jira Cloud, existente OU a criar sob gate humano (r02 FR-024 —
ver ETAPA 2.bis abaixo: reusar sempre primeiro; criacao so com
confirmacao explicita,
jira-setup.sh create-project). - Operador com acesso para gerar um API token classico
(
https://id.atlassian.com/manage-profile/security/api-tokens); para CRIAR um projeto novo, a conta do token precisa da permissao global Administer Jira (ETAPA 2.bis,403orienta a alternativa). - Scripts do plugin disponiveis:
jira-config.sh,jira-io.sh,jira-setup.sh(mesmo diretorioplugins/cstk-jira/scripts/).
Proximos passos
- Setup concluido (
jira-config.sh validateexit 0) ->/jira-convert <feature>para criar Epic/Tasks/Sub-tasks no Jira. /jira-sync statusa qualquer momento para ver conflitos/orfaos.
FLUXO DE EXECUCAO (ordem FIXA — ux CHK002)
1. SITE + PROJECT_KEY Perguntar site_host e project_key
|
2. CREDENCIAL Exibir comando p/ terminal proprio; validar remoto
|
2.bis REUSO/CRIACAO getProject; sem projeto, oferecer criacao sob gate
| (interativo: --confirm-key; autonomo: pedido de gate)
|
3. DESCOBERTA createmeta (R8) + transicoes (R5) — ver references/
|
4. MAPEAMENTO STATUS Perguntar pending/in_progress/pass/fail; validar
|
5. CONFIRMACAO TIPOS Listar tipos (id/name/hierarchyLevel/subtask); confirmar
|
6. FILTRO + BOARD Criar ou reusar (R9-R11)
|
7. TIPO DE LINK Listar tipos de R16 (rotulado); operador confirma
| ou pula (regra automatica, FASE 18.2)
|
8. GRAVACAO ATOMICA jira-setup.sh write-config (tudo ou nada)
What ships with it
4 files 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.
- 17d ago First seen · 467 lines · 121 tokens per session scan A 935dd159a032
jira-setup is a skill published in the GitHub repository JotJunior/cstk (24 stars, last pushed 6d ago), licensed MIT. It adds 121 tokens to every session and 6,502 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.