Borrowing it
Nothing to install: this file belongs to Traves-Theberge/Orchestra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Traves-Theberge/Orchestra/main/.codex/skills/maestro-jira/SKILL.mdgit clone --depth 1 https://github.com/Traves-Theberge/OrchestraWrote 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/skills/traves-theberge/orchestra/maestro-jira)<a href="https://agentmods.dev/skills/traves-theberge/orchestra/maestro-jira"><img src="https://agentmods.dev/badge/skills/traves-theberge/orchestra/maestro-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/skills/traves-theberge/orchestra/maestro-jira"><img src="https://agentmods.dev/badge/skills/traves-theberge/orchestra/maestro-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.00034 | $0.00521 |
| Opus 5.5 | $0.00014 | $0.00208 |
| Sonnet 5.5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
maestro-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 19d 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.
What it actually says
Jira for Maestro
Read maestro-integrations and orchestra-cli. Resolve the configured Jira site, project key, numeric issue ID, issue key, and browse URL separately from the Orchestra project ID. Never use a registered Orchestra UUID as a Jira project key, or send the jira: storage prefix as a native Jira issue ID.
Validate authentication and project access through the selected connection before claiming Jira access. Cloud uses email/API-token Basic auth when extra.jira_user is set; an empty user selects the intentional Bearer path. Server/Data Center uses username/token Basic auth. Cloud gateway/cloudId OAuth routing is unavailable; report that gap rather than rewriting credentials or assuming a token works.
Preserve the configured workflow-state map. Unmapped Jira states remain their reported states and are not automatically Backlog/Todo/Review. Jira Cloud structured descriptions are projected into readable text; rich document formatting is not preserved verbatim. Cloud comments use the version-aware document encoder. Read operations require the configured extra.default_project, add that project scope to JQL, and verify returned native project identity. Cloud uses enhanced /rest/api/3/search/jql; Server/Data Center uses /rest/api/2/search. Reads currently return a bounded first page; do not claim complete site/project coverage.
Creation uses the configured Jira project key, independently of Orchestra's local project UUID. The registry binds the local project only after native scope is verified; that binding does not establish exact requested workflow/assignee/provider metadata. Inspect the source issue and shared mutation receipt after an unconfirmed creation. The current generic update field allowlist does not implement assignee changes, and hosted queue is not a guarded transition. Use newly advertised dedicated capabilities when verified; otherwise report the unavailable operation without sending an unrelated legacy patch.
Treat issue creation/assignment, agent execution, PR linkage, review, and Done reconciliation as separate observations. A Jira development-panel link or issue mention is not a verified task PR URL. Use the exact persisted pr_url and matching GitHub/Azure repository identity; preserve the current reviewed head and checks when inspecting the PR.
Configure account connections in Orchestra settings, not AGENTS.md or skills. Jira Cloud REST guidance describes the native authentication and issue API; it does not certify Orchestra adapter parity.
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.
- 19d ago First seen · 19 lines · 34 tokens per session scan A 920a97afb852
maestro-jira is a skill published in the GitHub repository Traves-Theberge/Orchestra (26 stars, last pushed 10d ago), licensed Apache-2.0. It adds 34 tokens to every session and 521 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-10-06.
Other skills, from other repositories
agtx-oneshot
One-shot a whole project on an agtx board: decompose the goal, run every task unattended, unblock the workers, and merge each one. Use when the user wants a long autonomous run rather than a single session.
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
symphony-skill
Single Symphony operator router for Kanban tickets, service/TUI runs, WORKFLOW.md and prompt config, lane customization, delegation, production-ready app delivery planning, OneShot runs, repo and monorepo bootstrap, and worker failure triage.
kagan
Read a ticket, link threads, and move work through the native Kagan board when the user asks for ticket work.
superpm
Produce focused PM artifacts and verify them with a critic. Use for PRDs, strategy, OKRs, roadmaps, specs, research, analytics, GTM, growth, pricing, positioning, market signals, release notes, retros, and resume reviews.
Mochi-a-pm
Use this skill when the user or another AI needs project management, task tracking, priority assignment, timeline planning, or progress review. Mochi is a cute but deadly serious project manager AI.