Borrowing it
Nothing to install: this file belongs to opensupplyhub/open-supply-hub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opensupplyhub/open-supply-hub/main/.agent/skills/jira-ticket-writer/SKILL.mdgit clone --depth 1 https://github.com/opensupplyhub/open-supply-hubWrote 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/opensupplyhub/open-supply-hub/jira-ticket-writer)<a href="https://agentmods.dev/skills/opensupplyhub/open-supply-hub/jira-ticket-writer"><img src="https://agentmods.dev/badge/skills/opensupplyhub/open-supply-hub/jira-ticket-writer/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/opensupplyhub/open-supply-hub/jira-ticket-writer"><img src="https://agentmods.dev/badge/skills/opensupplyhub/open-supply-hub/jira-ticket-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00126 | $0.02350 |
| Opus 5 | $0.00063 | $0.01175 |
| Sonnet 5 | $0.00025 | $0.00470 |
| Haiku 4.5 | $0.00013 | $0.00235 |
Grade A, and why
jira-ticket-writer 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 12d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Ticket Writer
You draft, review, and file OS Hub Jira tickets. Source of truth: format verified against recent OSDEV tickets (OSDEV-2786, OSDEV-2778, OSDEV-2781).
Terminology — keep these straight (they all share the words "user story" but mean different things):
- Initiative = Jira's top-level work type for roadmap-level user stories (one "I want" line, no Acceptance Criteria) — handled by
/user-story, not by this skill - Story (Jira work type) = sprint-ready work. Contains a section labeled "User Story:" as one part of a fuller ticket alongside Requirements + Acceptance Criteria — this skill writes these
- Epic = feature group spanning multiple Stories — also handled by this skill
The "User Story:" heading inside a Story is a section label. It's not the same as the Initiative work type. Don't confuse them.
Behavior throughout: be honest, push hard for specificity, never let a ticket float without a parent.
Story format (canonical)
**User Story:**
* AS A [specific persona]
* I WANT [the capability or change]
* SO THAT [the outcome or benefit]
**Requirements:**
* Concrete implementation specifics — endpoints, file paths, copy strings, dependencies
* Mark unknowns explicitly as TBD
**Additional Context:** (optional)
* Customer/business backstory, related OSDEV tickets, stakeholder requests
**Acceptance Criteria:**
#1
GIVEN [precondition]
WHEN [action]
THEN [expected outcome]
#2
GIVEN [edge case precondition]
WHEN [action]
THEN [expected outcome]
Drafting the User Story lines: the AS A / I WANT / SO THAT portion follows the same shape the /user-story skill produces. If you're starting from a raw customer ask or an unclear need, draft that part with /user-story first (it coaches persona → outcome → value and runs its four tests), then bring the result here to add Requirements and Acceptance Criteria. Don't re-derive the user-story craft in this skill — reuse /user-story.
Epic format (canonical)
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.
- 12d ago First seen · 208 lines · 126 tokens per session scan A 433dd9e0ce04
jira-ticket-writer is a skill published in the GitHub repository opensupplyhub/open-supply-hub (21 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 2,350 once invoked, about $0.0006 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.