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 agentmods add commands/james-prodopen/emcmd/jira-duplicate-bugsgit clone --depth 1 https://github.com/james-prodopen/emcmdWrote 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/james-prodopen/emcmd/jira-duplicate-bugs)<a href="https://agentmods.dev/commands/james-prodopen/emcmd/jira-duplicate-bugs"><img src="https://agentmods.dev/badge/commands/james-prodopen/emcmd/jira-duplicate-bugs.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 | $0.00000 | $0.00747 |
| Opus 5 | $0.00000 | $0.00374 |
| Sonnet 5 | $0.00000 | $0.00149 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
jira-duplicate-bugs 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 4d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find potential duplicate bugs in a Jira project. Provide PROJECT_KEY here: $ARGUMENTS.
Workflow
Follow these instructions explicitly:
- Use
acli jira auth statusto get the "Site" value, which will be used to generate URLs later - Use
acli jira workitem search --json --jql "project={PROJECT_KEY} and issuetype=Bug" --paginateto fetch all work items in the project, iterating through all pages if need be - Output a working table of unique work item pairs, where at least one work item in the pair does not have status.name of "Done" - for example, assuming you have work items A and B
- if (A status.name != "Done" AND B status.name != "Done") OR (A status.name = "Done" AND B status.name != "Done") OR (A status.name != "Done" AND B status.name = "Done") include a row (A,B) in the table
- do not create a duplicative row (B,A) in addition to (A,B)
- table schema should be (A.key | A.summary | B.key | B.summary)
- DO NOT truncate summary text
- Did you output a working table in step 3? If not, go back to step 3 and output a working table - DO NOT proceed unless that has been completed
- Analyze all work item PAIRS in the previously created working table to identify potential duplicates based on similar summary text
- when analyzing, consider only a single row at a time to avoid finding work item pairs that both have status.name = "Done"
- For each potential duplicate pair, use
acli jira workitem link list --key "{key}" --jsonon BOTH of the work items to check if they are already linked to each other- you need to check both work items because that acli command supports "duplicates" but not "is duplicated by" relationships
- If the pair of work items is not already linked, use
acli jira workitem view "{key}" --fields "issuetype,summary,description"for both work items to review them in additional detail and increase confidence that they are duplicates - For each pair of work items that are duplicates, generate URLs for each work item using the format:
https://{site}/browse/{key}
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.
- 4d ago First seen · 42 lines · 0 tokens per session scan A 11b96555be95
jira-duplicate-bugs is a command published in the GitHub repository james-prodopen/emcmd (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 747 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
promote
Refine scv/raw/ material into a scv/promote/ - - / folder with PLAN.md + TESTS.md. Optionally updates the docs knowledge graph. Interactive; no files written without user approval. Use whenever the user wants a change planned, specced, or broken down before implementation — 'plan this', 'write a spec', 'what should we…
work
Implement a scv/promote/ / plan. Reads PLAN.md + TESTS.md, proposes/loads Related Documents as needed, runs the tests, and optionally archives on success. Use whenever the user wants an existing plan implemented — 'build it', 'implement the plan', 'let's do it' — not only when they type /scv:work. Never implement a…
help
Show SCV workflow + diagnose project + recommend next step. With an argument, talk through an idea OR search the archive for past work — SCV picks the right mode from your wording. Use whenever the user is thinking out loud about a change, asks what to do next, asks what SCV can do, or wants to find past work — not…
codegen
TDD-first codegen for a scv/promote/ / plan. Verifies TESTS fail first (Red), then iteratively writes the minimum code to pass each case (Green). Hands off archive/PR/regression to /scv:work. Use whenever the user wants a plan implemented test-first — 'TDD', 'tests first', 'red-green' — not only when they type…
deck
Turn a markdown planning doc into a spec-grade 기획서 HTML — a buildless, self-contained document by default, or an on-screen slide presentation when you ask for one. Deterministic md→deck transform + a quality/gap lint; the raw markdown travels with it. Use whenever the user wants a planning document turned into…
regression
Run accumulated regression across scv/archive//TESTS.md (and optionally promote/) with supersede/obsolete skip graph. On failure, triage each slug via AskUserQuestion (regression / obsolete / flaky). Use whenever the user asks whether past features still pass, or before archiving anything — 'run the tests', 'is…