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.
git 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/gh-jira-1on1-prep)<a href="https://agentmods.dev/commands/james-prodopen/emcmd/gh-jira-1on1-prep"><img src="https://agentmods.dev/badge/commands/james-prodopen/emcmd/gh-jira-1on1-prep/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/james-prodopen/emcmd/gh-jira-1on1-prep"><img src="https://agentmods.dev/badge/commands/james-prodopen/emcmd/gh-jira-1on1-prep.svg" alt="Reviewed on agentmods" width="80" 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.00741 |
| Opus 5 | $0.00000 | $0.00370 |
| Sonnet 5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
gh-jira-1on1-prep 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 9d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare for a 1-on-1 meeting with a dev. Provide EMAIL (for Jira) and GH_USERNAME (for GitHub) here: $ARGUMENTS.
Workflow
Follow these instructions explicitly:
- Parse $ARGUMENTS to extract EMAIL and GH_USERNAME (space-separated, e.g., "[email protected] github-username")
- Use
acli jira workitem search --json --jql "assignee = '{EMAIL}' and (sprint in openSprints() OR resolved >= -2w) ORDER BY resolved DESC" --fields "summary" --limit 50to find their work items in current sprint or resolved in last 2 weeks - For each work item, use
acli jira workitem view {key}to fetch detailed information including description, comments, and status - Use
gh search prs --author {GH_USERNAME} --updated ">={today - 14 days}" --json number,repository --limit 50to find their recent PRs from the last 2 weeks - For each PR, use
gh pr view {number} --repo {owner/repo} --json number,title,author,updatedAt,state,isDraft,mergeable,reviewDecision,statusCheckRollup,reviewRequests,comments,reviews,urlto get detailed PR information - For each PR, analyze comments and reviews to identify if other users (with different usernames) assisted with the work - look for substantive code contributions, pair programming mentions, or significant technical guidance
- Use
acli jira auth statusto get the "Site" value, which will be used to generate URLs later (to fill in {jira_site}) - Organize and summarize the information for the 1-on-1 meeting
Analysis
Provide insights on:
- Completed work - Work items resolved in the last 2 weeks
- In-progress work - Work items currently in progress in the sprint
- Blockers - Any items that appear blocked or stalled
- PR status - Draft PRs, open PRs, merged PRs, PR review feedback, PRs waiting on review
- Quality signals - Failed CI checks, requested changes, merge conflicts
- Velocity - Number of items completed vs in progress
- Collaboration - Other users who assisted with PRs (identified by their contributions in comments/reviews)
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.
- 9d ago First seen · 48 lines · 0 tokens per session scan A bac5a0690e4f
gh-jira-1on1-prep 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 741 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
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
project-health
Audit and manage project configuration — permissions, context, docs.
adopt-roadmap.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
board-csk
Team board — see who holds which item, claim one, hand it over, complete it.