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.
/plugin marketplace add mulhamna/jira-commandsnpx agentmods add plugins/mulhamna/jira-commands/marketplacegit clone --depth 1 https://github.com/mulhamna/jira-commandsWrote 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/plugins/mulhamna/jira-commands/marketplace)<a href="https://agentmods.dev/plugins/mulhamna/jira-commands/marketplace"><img src="https://agentmods.dev/badge/plugins/mulhamna/jira-commands/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
jira-commands marketplace 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 6d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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.
- 6d ago First seen · 33 lines scan A a0a279f50d06
jira-commands marketplace is a plugin published in the GitHub repository mulhamna/jira-commands (49 stars, last pushed 2d ago), with no licence file. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
jira-assistant-skills
Complete JIRA automation suite with 14 specialized skills - issue management, agile workflows, time tracking, service management, bulk operations, and more.
jira
Comprehensive Jira integration with auto-detection of issue keys.
jira-mcp-ai
Jira Cloud tools for Claude Code: JQL search, issue reads, and writes behind a plan/apply gate.
claude-jira-skill marketplace
Plugin marketplace listing 1 plugin: claude-jira-skill.
claude-jira-skill
Claude Code skill for Jira — fetch tickets, search with JQL, manage issues, and generate team digest reports.
atlassian
Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.