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/mturac/everything-openai-codexWrote 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/mturac/everything-openai-codex/jira)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/jira"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/jira/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/mturac/everything-openai-codex/jira"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/jira.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.00027 | $0.00741 |
| Opus 5.5 | $0.00011 | $0.00296 |
| Sonnet 5.5 | $0.00005 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
jira 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 1mo 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Command
Interact with Jira tickets directly from your workflow — fetch tickets, analyze requirements, add comments, and transition status.
Usage
/jira get <TICKET-KEY> # Fetch and analyze a ticket
/jira comment <TICKET-KEY> # Add a progress comment
/jira transition <TICKET-KEY> # Change ticket status
/jira search <JQL> # Search issues with JQL
What This Command Does
- Get & Analyze — Fetch a Jira ticket and extract requirements, acceptance criteria, test scenarios, and dependencies
- Comment — Add structured progress updates to a ticket
- Transition — Move a ticket through workflow states (To Do → In Progress → Done)
- Search — Find issues using JQL queries
How It Works
/jira get <TICKET-KEY>
- Fetch the ticket from Jira (via MCP
jira_get_issueor REST API) - Extract all fields: summary, description, acceptance criteria, priority, labels, linked issues
- Optionally fetch comments for additional context
- Produce a structured analysis:
Ticket: PROJ-1234
Summary: [title]
Status: [status]
Priority: [priority]
Type: [Story/Bug/Task]
Requirements:
1. [extracted requirement]
2. [extracted requirement]
Acceptance Criteria:
- [ ] [criterion from ticket]
Test Scenarios:
- Happy Path: [description]
- Error Case: [description]
- Edge Case: [description]
Dependencies:
- [linked issues, APIs, services]
Recommended Next Steps:
- /plan to create implementation plan
- `tdd-workflow` skill to implement with tests first
/jira comment <TICKET-KEY>
- Summarize current session progress (what was built, tested, committed)
- Format as a structured comment
- Post to the Jira ticket
/jira transition <TICKET-KEY>
- Fetch available transitions for the ticket
- Show options to user
- Execute the selected transition
/jira search <JQL>
- Execute the JQL query against Jira
- Return a summary table of matching issues
Prerequisites
This command requires Jira credentials. Choose one:
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.
- 1mo ago First seen · 107 lines · 27 tokens per session scan A 0503ced85e11
jira is a command published in the GitHub repository mturac/everything-openai-codex (86 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 741 once invoked, about $0.0001 per session on Opus 5.5. 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-09-03.
Other commands, from other repositories
morning
The coffee report — cross-project map deltas, arrives on its own (scheduled).
handoff
Refresh the project hand-off before ending the session.
convert-to-plan
Convert planning artifacts (lite-plan, workflow session, markdown) to issue solutions.
execute
Execute queue with DAG-based parallel orchestration (one commit per solution).
queue
Form execution queue from bound solutions using issue-queue-agent (solution-level).
from-brainstorm
Convert brainstorm session ideas into issue with executable solution for parallel-dev-cycle.