Borrowing it
Nothing to install: this file belongs to stolostron/jira-mcp-server. 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/stolostron/jira-mcp-server/main/.claude/commands/myissues.mdgit clone --depth 1 https://github.com/stolostron/jira-mcp-serverWrote 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/commands/stolostron/jira-mcp-server/myissues)<a href="https://agentmods.dev/commands/stolostron/jira-mcp-server/myissues"><img src="https://agentmods.dev/badge/commands/stolostron/jira-mcp-server/myissues.svg" alt="Measured on agentmods" 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.00622 |
| Opus 5 | $0.00000 | $0.00311 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
myissues 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 8d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
My Issues Command
Show a table of all my Jira issues for a specific ACM release version.
Instructions
Step 1: Determine ACM Version
Check if a version was already selected earlier in this conversation (from a previous /myissues invocation). If so, reuse that version silently — do NOT prompt again.
Only use AskUserQuestion to ask for the version if:
- This is the first time
/myissuesis run in this session, OR - The user explicitly asks to change the version (e.g., "show me 2.16.0 issues", "switch to ACM 2.18.0")
When prompting, pre-fill with the most likely current version based on context. If CLAUDE.md mentions a fix_version, use the next minor version as the default guess (e.g., if fix_version is "ACM 2.16.0", guess "ACM 2.17.0"). Common options:
- ACM 2.17.0 (Recommended)
- ACM 2.16.0
- ACM 2.18.0
Step 2: Search for Issues
Run TWO parallel Jira searches using search_issues:
Query 1 — Fix Version:
project = ACM AND fixVersion = "<version>" AND (assignee = "[email protected]" OR reporter = "[email protected]") ORDER BY status ASC, priority DESC
Query 2 — Target Version:
project = ACM AND "Target Version" = "<version>" AND (assignee = "[email protected]" OR reporter = "[email protected]") ORDER BY status ASC, priority DESC
Merge the results, deduplicating by issue key.
Step 3: Check for Recently Worked Issues
Before rendering the table, review the current conversation history. If you performed actions on any issues earlier in this session (e.g., added comments, transitioned, updated, summarized, created tasks for, or otherwise interacted with an issue), then:
- Note which issues were worked on
- Exclude them from the table
- State clearly at the top: "Excluded issues worked on in this session: ACM-XXXXX, ACM-YYYYY"
This keeps the table focused on issues that still need attention.
Step 4: Render the Table
Present the results as a markdown table with these columns:
| Key | Type | Summary | Status | Priority | Fix Version | Target Version |
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.
- 8d ago First seen · 62 lines · 0 tokens per session scan A 388cc12d446f
myissues is a command published in the GitHub repository stolostron/jira-mcp-server (2 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 622 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-08-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.