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-external-dependenciesgit 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-external-dependencies)<a href="https://agentmods.dev/commands/james-prodopen/emcmd/jira-external-dependencies"><img src="https://agentmods.dev/badge/commands/james-prodopen/emcmd/jira-external-dependencies.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.00663 |
| Opus 5 | $0.00000 | $0.00331 |
| Sonnet 5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
jira-external-dependencies 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find external dependencies for work items in a Jira project. Provide PROJECT_KEY here: $ARGUMENTS.
Workflow
Follow these instructions explicitly. Under absolutely no circumstances are you to use acli. If the required MCP tools are not available, simply share the content in the Dependencies section below with the user and do absolutely nothing else.
- Use
mcp__atlassian__getAccessibleAtlassianResourcesto get the cloudId (returned simply as "id") and url (which will be the {site_url} used later to generate links to work items) - Use
mcp__atlassian__searchJiraIssuesUsingJqlwith cloudId from step 1, jql="project={PROJECT_KEY}", and fields=["summary","issuelinks"]
- do not specify a maxResults - iterate through all pages using nextPageToken
- For each work item (let's call this work item x) returned, examine the x.fields.issuelinks array
- For each link in issuelinks (let's call them y), check if:
- type.name = "Blocks"
- The link has an "inwardIssue" field but NOT an "outwardIssue" field
- The inwardIssue.key has a different project prefix than {PROJECT_KEY}
- If all conditions are met, x has an external dependency on y
- For each external dependency found, use
mcp__atlassian__getJiraIssuewith the cloudId and issueIdOrKey=inwardIssue.key to get full details
- do not pass a value for "fields" or "expand"
- Summarize all external dependencies with their current state
External Dependency Detection
An external dependency is identified when:
- A work item in {PROJECT_KEY} has a "Blocks" link with an inwardIssue (meaning it is blocked by that issue)
- The inwardIssue.key starts with a different project prefix than {PROJECT_KEY}
- Example: If PROJECT_KEY is "ABC", then ABC-123 blocked by ABC-456 is internal, but ABC-123 blocked by DEF-456 is external
Output
For each work item (x) that has external dependencies (y), provide:
External Dependencies
"{site_url}/browse/{x_key}" - {x_summary}:
(for each dependency, y):
\n
→ "is blocked by {site_url}/browse/{x_key}"
Brief natural language summary of the response from mcp__atlassian__getJiraIssue tool call
- be sure to note status, created and last updated
- never include times in dates
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 · 47 lines · 0 tokens per session scan A 7932d48572cc
jira-external-dependencies 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 663 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…