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-comment-blockersgit 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-comment-blockers)<a href="https://agentmods.dev/commands/james-prodopen/emcmd/jira-comment-blockers"><img src="https://agentmods.dev/badge/commands/james-prodopen/emcmd/jira-comment-blockers.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.00542 |
| Opus 5 | $0.00000 | $0.00271 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
jira-comment-blockers 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 5d 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize work item blockers in the current sprint. Optionally provide a PROJECT_KEY here: $ARGUMENTS.
Workflow
Follow these instructions explicitly:
- If a PROJECT_KEY is provided in $ARGUMENTS, use
acli jira workitem search --json --jql "project = {PROJECT_KEY} AND sprint IN openSprints() and status != Done ORDER BY updated ASC" --fields "summary" --limit 50to search for work items in that project - Otherwise, use
acli jira workitem search --json --jql "sprint IN openSprints() and status != Done ORDER BY updated ASC" --fields "summary" --limit 50to find work items in the current sprint that aren't done - For each work item found, use
acli jira workitem comment list --key {KEY}to fetch all comments on the work item - Analyze each work item's comments for mentions of blockers
- Use
acli jira auth statusto get the "Site" value, which will be used to generate URLs later (to fill in {jira_site}) - Report all blocked work items with concise blocker summaries
Blocker Detection
Check for these common blocker indicators in comments:
- Explicit blocker mentions - Comments containing words like "blocked", "blocker", "blocking", "can't proceed"
- Dependency issues - Waiting on other teams, external dependencies, or upstream work
- Technical blockers - Infrastructure issues, environment problems, access issues
- Resource blockers - Waiting for design, waiting for requirements, waiting for product management, waiting for approval
- Third-party blockers - Vendor delays, API issues, external service problems
- Review blockers - Waiting on any sort of review, e.g. waiting for code review, waiting for QA, waiting for stakeholder approval
Output
Report only blocked work items (do not include unblocked items in the summary). For each blocked item: work item key, summary, URL (generated using format: https://{jira_site}/browse/{key}) and concise blocker summary extracted from comments (e.g., "Blocked by: waiting on API access from Platform team", "Blocked by: infrastructure issues in staging environment", "Blocked by: pending design approval from Product")
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.
- 5d ago First seen · 31 lines · 0 tokens per session scan A 8965d7a54efd
jira-comment-blockers 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 542 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…