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 kirti/jira-ticket-builder-skill --skill skillgit clone --depth 1 https://github.com/kirti/jira-ticket-builder-skillWrote 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/kirti/jira-ticket-builder-skill/skill)<a href="https://agentmods.dev/skills/kirti/jira-ticket-builder-skill/skill"><img src="https://agentmods.dev/badge/skills/kirti/jira-ticket-builder-skill/skill/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/kirti/jira-ticket-builder-skill/skill"><img src="https://agentmods.dev/badge/skills/kirti/jira-ticket-builder-skill/skill.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.00213 | $0.03923 |
| Opus 5 | $0.00106 | $0.01962 |
| Sonnet 5 | $0.00043 | $0.00785 |
| Haiku 4.5 | $0.00021 | $0.00392 |
Grade A, and why
jira-ticket-builder 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 9d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Ticket Builder
Converts rough input into a structured, ready-to-paste Jira ticket. Built around the pipeline:
ROUGH INPUT → Understand Input → Extract Facts → Fill Missing Data / Ask →
Generate Ticket → Validate → Jira Ticket
Step 0 — Single ticket vs. decomposition
Before running the single-ticket pipeline below, check the input's shape:
- Single ticket: one bug, one feature ask, one clear unit of work → proceed with Steps 1-5 as below.
- Decomposition: a rough requirements document — meeting notes, a product brief, an email thread, a spec with multiple asks and open questions bundled together — where a single ticket would be too large or would hide independently-shippable pieces → use Decomposition Mode below instead of Steps 1-5.
Signal for decomposition mode: multiple distinct capabilities mentioned, a "Questions:" section, or the user says things like "break this down," "turn this into stories," or pastes a document rather than a single ask.
Decomposition Mode
For a rough requirements document that needs to become multiple linked Jira stories with full traceability and an explorable dashboard.
D1 — Analyze the document
Read the whole document first. Extract, without inventing:
- Business context — objectives, actors (who's involved), business rules, and the business
flow (actor → action → system, as an ordered sequence if the doc describes a process). Where a
step has a UI screen or a callable API/system, note it (
ui_screen/api) — this is what lets the Customer Journey diagram show the full stack per step, not just the business narrative. - Business requirements — the business objective/problem/value being addressed
- Functional requirements — what the system must do
- Non-functional requirements — performance, security, accessibility, compliance
- Ambiguities — anything incomplete, contradictory, vague, or missing acceptance criteria/technical decisions
Mark every requirement, objective, and business rule confidence: "confirmed" (stated in the
doc) or "inferred" (you concluded it from context) — never leave this implicit.
What ships with it
8 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.
- 9d ago First seen · 285 lines · 213 tokens per session scan A 757a926d60f1
jira-ticket-builder is a skill published in the GitHub repository kirti/jira-ticket-builder-skill (2 stars, last pushed 29d ago), licensed MIT. It adds 213 tokens to every session and 3,923 once invoked, about $0.0011 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
team-lead-reference
Provides model routing rules, validates delegation prerequisites, supplies cost tracking templates, defines dead-letter queue formats for Team Lead orchestration. Load when assigning tasks to agents, choosing model tiers, starting delegation session, running multi-agent workflow, delegating work, choosing which model…
orchestration-protocols
Coordinate multiple agents: parallel spawning, health monitoring, circuit breakers, escalation. Use for parallel agents, agent timeouts, fan-out tasks, multi-agent delegation.
trello-task-management
Create and manage Trello cards, checklists, and boards for kanban workflows. Use when the user says: 'create a kanban board', 'add a task card', 'move card to sprint', or 'track project board'.
jira-management
Create and update Jira issues, epics, and sprints; manage backlog and sprint transitions. Use when you say: 'create a ticket', 'open a story', 'link an epic', 'start a sprint', or 'search the backlog'.
linear-task-management
Creates and names Linear issues, assigns labels and priorities, manages status transitions, and links issues to PRs. Use when decomposing features into tasks or resuming interrupted sessions. Trigger terms: tickets, backlog, task breakdown, project board, sprint planning.
session-checkpoints
Saves, restores session state including task progress, file changes, delegation history. Use when saving progress, resuming interrupted work, picking up where you left off, or checkpointing current work.