Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/abdullahkhawer/devops-skillsnpx agentmods add skills/abdullahkhawer/devops-skills/maintenance-create-ticket-on-jiraWrote 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/abdullahkhawer/devops-skills/maintenance-create-ticket-on-jira)<a href="https://agentmods.dev/skills/abdullahkhawer/devops-skills/maintenance-create-ticket-on-jira"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/maintenance-create-ticket-on-jira/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/abdullahkhawer/devops-skills/maintenance-create-ticket-on-jira"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/maintenance-create-ticket-on-jira.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.00026 | $0.02315 |
| Opus 5 | $0.00013 | $0.01157 |
| Sonnet 5 | $0.00005 | $0.00463 |
| Haiku 4.5 | $0.00003 | $0.00231 |
Grade A, and why
maintenance-create-ticket-on-jira 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Maintenance Upgrade Ticket on Jira Skill
Run this skill when asked to create or update a Jira maintenance upgrade ticket based on maintenance upgrade check file(s) under maintenance-checks directory at the root of the working directory.
This skill reads maintenance upgrade check files, extracts the details related to Jira ticket title and description, then creates or updates the corresponding issue in the configured Jira project.
Configuration
Update the values below with your Jira project details before using this skill:
| Setting | Value |
|---|---|
| Atlassian Site | <your-site>.atlassian.net |
| Jira Project Key | <YOUR_PROJECT_KEY> (e.g. OPS, INFRA) |
Step 1 — Locate maintenance upgrade check file(s)
Find all maintenance upgrade check files in the ./maintenance-checks/ directory:
ls ./maintenance-checks/maintenance-check-*.md
If the user specified a particular file, use that. If multiple files are found and none was specified, list them and ask the user which one(s) to process. Process one file at a time — after completing all steps for a file, return to this step and process the next selected file.
Step 2 — Parse the maintenance upgrade file
Read the maintenance upgrade check file and extract:
- Maintenance upgrade required — from the
## Decision→**Maintenance upgrade required:**field - Ticket title — from the
## Jira Ticket→**Title:**field - Parent — from the
## Jira Ticket→**Parent:**field - Label — from the
## Jira Ticket→**Label:**field - Story Points — from the
## Jira Ticket→**Story Points:**field - Refined — from the
## Jira Ticket→**Refined:**field - Ticket description — from the
## Jira Ticket→**Description:**block (everything after**Description:**to the end of the file)
If any extracted field or block is missing or blank, report: "Cannot proceed: '<field-name>' is missing in <filename>" and stop.
If Maintenance upgrade required: No, inform the user that no maintenance upgrade ticket is needed for this file and stop.
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 · 212 lines · 26 tokens per session scan A c49172678454
maintenance-create-ticket-on-jira is a skill published in the GitHub repository abdullahkhawer/devops-skills (7 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 2,315 once invoked, about $0.0001 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
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…
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
gh-issues
Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via gh. Covers issue templates, project board assignment, title conventions, and required gh scopes.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
flow-parallel
Decompose and execute large changes, migrations, or multi-issue fixes in parallel with quality gates.