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 kubiyabot/skill --skill jira-skillgit clone --depth 1 https://github.com/kubiyabot/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/kubiyabot/skill/jira-skill)<a href="https://agentmods.dev/skills/kubiyabot/skill/jira-skill"><img src="https://agentmods.dev/badge/skills/kubiyabot/skill/jira-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/kubiyabot/skill/jira-skill"><img src="https://agentmods.dev/badge/skills/kubiyabot/skill/jira-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.00000 | $0.01249 |
| Opus 5.5 | $0.00000 | $0.00500 |
| Sonnet 5.5 | $0.00000 | $0.00250 |
| Haiku 4.5 | $0.00000 | $0.00125 |
Grade A, and why
jira-skill 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 1mo 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Skill
Jira project management and issue tracking operations.
Overview
This skill provides comprehensive access to the Jira REST API and Agile API for managing issues, projects, sprints, and boards.
Requirements
- Jira Cloud or Jira Data Center instance
- API token (Cloud) or personal access token (Data Center)
- User email address for authentication
Configuration
export SKILL_JIRA_URL=https://your-domain.atlassian.net
export [email protected]
export SKILL_JIRA_TOKEN=your_api_token
Generate a token at: https://id.atlassian.com/manage-profile/security/api-tokens
Tools (25)
User Tools
myself- Get current authenticated user informationuser-search- Search for users by name or email
Issue Search
search- Search issues using JQL (Jira Query Language)
Issue CRUD
issue-get- Get detailed issue informationissue-create- Create a new issueissue-update- Update an existing issueissue-delete- Delete an issueissue-assign- Assign or unassign an issue
Issue Workflow
transitions- Get available transitions for an issueissue-transition- Move issue to a new status
Comments
comment-list- List comments on an issuecomment-add- Add a comment to an issuecomment-update- Update an existing comment
Work Logs
worklog-list- List work logs on an issueworklog-add- Log time spent on an issue
Projects
project-list- List all accessible projectsproject-get- Get project details
Agile - Boards
board-list- List agile boardsboard-get- Get board details
Agile - Sprints
sprint-list- List sprints for a boardsprint-get- Get sprint details
Metadata
priorities- Get available priority levelsissue-types- Get available issue types (optionally per project)
JQL Query Examples
Basic Queries
project = PROJ- Issues in project PROJassignee = currentUser()- My assigned issuesstatus = "In Progress"- Issues in progress
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.
- 1mo ago First seen · 221 lines · 0 tokens per session scan A 5e685fc7aa67
jira-skill is a skill published in the GitHub repository kubiyabot/skill (19 stars, last pushed 8mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,249 tokens. 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-03.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…