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 skills add Yoshikemolo/mcp-jira-devflow --skill orchestrationgit clone --depth 1 https://github.com/Yoshikemolo/mcp-jira-devflowWrote 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/yoshikemolo/mcp-jira-devflow/orchestration)<a href="https://agentmods.dev/skills/yoshikemolo/mcp-jira-devflow/orchestration"><img src="https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/orchestration/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/yoshikemolo/mcp-jira-devflow/orchestration"><img src="https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/orchestration.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.00029 | $0.00516 |
| Opus 5 | $0.00015 | $0.00258 |
| Sonnet 5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
orchestration 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.
What it actually says
Orchestration Skill
Coordinate multi-step workflows with planning, execution, and rollback.
Allowed Operations
- Create execution plans
- Execute plans step-by-step
- Coordinate between skills
- Track execution state
- Handle rollbacks
Forbidden Operations
- Execute without plan approval
- Skip plan validation
- Ignore step failures
- Parallel execution without explicit flag
- Modify plan during execution
Execution Phases
1. Plan Phase
- Output all steps
- Identify tools and risks
- NO side effects
- Requires approval
2. Validation Phase
- Validate all inputs
- Check permissions
- Dry-run each step
3. Execution Phase
- Execute step-by-step
- Abort on error
- Track state for rollback
4. Rollback Phase (if needed)
- Execute in reverse order
- Log all actions
- Report final state
Quick Plan Structure
plan:
id: "plan-001"
name: "Implement Feature"
steps:
- id: "step-1"
skill: "git-operations"
action: "create-branch"
params:
name: "feature/PROJ-123"
rollback:
action: "delete-branch"
- id: "step-2"
skill: "jira-write"
action: "transition"
params:
issue: "PROJ-123"
status: "In Progress"
dependsOn: ["step-1"]
For complete plan examples, see PLAN-EXAMPLES.md.
For rollback patterns, see ROLLBACK-STRATEGIES.md.
Error Handling
| Scenario | Action |
|---|---|
| Single step failure | Pause and report |
| Multiple failures | Abort and rollback |
| Rollback failure | Alert for manual intervention |
Example Usage
Create a plan to implement feature PROJ-123
Execute the approved plan step by step
Resume plan execution from step 3
Rollback the last failed plan
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 99 lines · 29 tokens per session scan A 9dd36772435d
orchestration is a skill published in the GitHub repository Yoshikemolo/mcp-jira-devflow (5 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 516 once invoked, about $0.0001 per session on Opus 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 skills, from other repositories
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
finance
Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions. Use when building financial models, analyzing statements, or making investment decisions.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.