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 agentmods add skills/yoshikemolo/mcp-jira-devflow/devflow-planningnpx skills add Yoshikemolo/mcp-jira-devflow --skill devflow-planninggit 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/devflow-planning)<a href="https://agentmods.dev/skills/yoshikemolo/mcp-jira-devflow/devflow-planning"><img src="https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/devflow-planning.svg" alt="Measured on agentmods" 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.00035 | $0.00716 |
| Opus 5 | $0.00017 | $0.00358 |
| Sonnet 5 | $0.00007 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
devflow-planning 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 5d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevFlow Planning Skill
Sprint planning, velocity analysis, and predictive analytics for agile teams.
Allowed Operations
- Analyze sprint velocity and trends
- Generate capacity forecasts
- Predict sprint success probability
- Recommend optimal sprint load
- Identify spillover risks
- Cross-project dependency mapping
- Generate documentation from issues
- Compile release notes
Forbidden Operations
These require explicit user approval:
- Auto-commit sprint changes
- Modify issue estimates without review
- Move issues to sprints automatically
- Create issues from predictions
Sprint Planning Workflow
1. Analyze velocity → Get historical data
2. Calculate capacity → Team availability
3. Recommend load → Based on trends
4. Assess risks → Per-issue spillover
5. Validate plan → Sprint success prediction
Quick Velocity Reference
| Metric | Description | Use For |
|---|---|---|
| Avg Velocity | Points completed per sprint | Baseline planning |
| Trend Direction | Increasing/Stable/Decreasing | Adjust forecasts |
| Completion Rate | Done vs Committed ratio | Risk assessment |
| Variance | Sprint-to-sprint deviation | Confidence levels |
For complete velocity patterns, see VELOCITY-PATTERNS.md.
Quick Capacity Reference
Team Capacity = Sum(member availability × sprint days)
Recommended Load = Avg Velocity × (1 - Buffer%)
Buffer Guidelines:
- Stable team: 10%
- New members: 20%
- High uncertainty: 30%
For sprint planning details, see SPRINT-PLANNING-GUIDE.md.
Proactive Recommendations
| Context | Trigger | Action |
|---|---|---|
| Sprint >80% filled | Overcommit risk | Suggest scope reduction |
| Velocity declining 3+ sprints | Trend alert | Recommend retrospective focus |
| Issue blocked >2 days | Dependency risk | Escalate blocker |
| Unestimated work in sprint | Planning gap | Flag for refinement |
| Branch stale >5 days | GitFlow alert | Review or close |
What ships with it
5 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.
- 5d ago First seen · 110 lines · 35 tokens per session scan A 030c085bd3c9
devflow-planning is a skill published in the GitHub repository Yoshikemolo/mcp-jira-devflow (5 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 716 once invoked, about $0.0002 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.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.
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.
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.