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/HigorAlves/orcWrote 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/higoralves/orc/jira)<a href="https://agentmods.dev/commands/higoralves/orc/jira"><img src="https://agentmods.dev/badge/commands/higoralves/orc/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/higoralves/orc/jira"><img src="https://agentmods.dev/badge/commands/higoralves/orc/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.00054 | $0.02143 |
| Opus 5.5 | $0.00022 | $0.00857 |
| Sonnet 5.5 | $0.00011 | $0.00429 |
| Haiku 4.5 | $0.00005 | $0.00214 |
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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:jira
Single entry point for Jira operations from inside an orc session. Wraps acli (the supported Atlassian CLI) and integrates with .orc/ state so a ticket key, once bound, follows the work through /orc:status, /orc:resume, and /orc:ship.
For building a whole Epic→Story→Task hierarchy from a feature brief or PRD (micro-PRD epic, templated children, concurrency-sliced tasks), use /orc:jira-breakdown — it composes this command's primitives per the orc:jira-hierarchy contract.
Always invoke orc:jira-cli before running any acli command — it's the reference for flags, auth, and pitfalls.
Verbs
| Verb | What it does | Touches .orc/? |
|---|---|---|
create |
Create a top-level ticket | optionally auto-binds the new key |
subtask |
Create a sub-task under a parent | optionally auto-binds the new key |
link |
Link two existing tickets (Jira-side relationship) | no |
bind <KEY> |
Attach <KEY> to the current orc session |
yes (writes jiraTicket) |
unbind |
Remove the bound ticket from the current session | yes (clears jiraTicket) |
view [KEY] |
Show a ticket; defaults to current session's bound key | no |
transition [KEY] --to "<status>" |
Move a ticket to a new status | no |
search --jql "<query>" |
List tickets matching JQL | no |
Workflow
Phase 0 — Preflight
- Invoke
orc:jira-cli. Read it; the rest of this command assumes you know theacliflag conventions documented there. - Run
acli jira auth status. If it exits non-zero, surface the auth-login hint from the skill and stop. Never try to invoke a mutatingaclicommand without confirming auth first.
Phase 1 — Dispatch on verb
Parse the first positional arg. If missing, surface AskUserQuestion with the eight verbs above. If the verb isn't recognized, surface the same prompt.
Then jump to the matching section below.
Verb: create
acli jira workitem create \
--summary "<summary>" \
--project "<KEY>" \
--type "<Task|Story|Bug|Epic>" \
[--assignee "@me|email"] \
[--description "<text>"] \
[--label "<a,b>"] \
--json
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 · 183 lines · 54 tokens per session scan A 6995d2a4ca93
jira is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 2,143 once invoked, about $0.0002 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-08-31.
Other commands, from other repositories
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
scout-work
Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
status
Show current execution status with progress, dependencies, file ownership, and parallelization opportunities.