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 mvilrokx/claude-skills --skill jira-workflowgit clone --depth 1 https://github.com/mvilrokx/claude-skillsWrote 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/mvilrokx/claude-skills/jira-workflow)<a href="https://agentmods.dev/skills/mvilrokx/claude-skills/jira-workflow"><img src="https://agentmods.dev/badge/skills/mvilrokx/claude-skills/jira-workflow/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/mvilrokx/claude-skills/jira-workflow"><img src="https://agentmods.dev/badge/skills/mvilrokx/claude-skills/jira-workflow.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.00151 | $0.02673 |
| Opus 5 | $0.00076 | $0.01337 |
| Sonnet 5 | $0.00030 | $0.00535 |
| Haiku 4.5 | $0.00015 | $0.00267 |
Grade A, and why
jira-workflow 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 12d 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Workflow Skill
Manage development workflows using Jira tickets. Supports four core operations: listing work, creating work, assigning work, and doing work.
Prerequisites
- Access to Jira via MCP Atlassian tools
- Git repository in the current workspace
- Appropriate Jira project permissions
Quick Reference
| User Intent | Workflow |
|---|---|
| "List my work" / "Show my tickets" | → List Work |
| "Create a ticket" / "Add work" | → Create Work |
| "Assign PROJ-123 to John" | → Assign Work |
| "Add label to PROJ-123" | → Manage Labels |
| "List components" | → List Components |
| "Do work" / "Work on PROJ-123" | → Do Work |
List Work
Display the user's assigned Jira tickets.
Steps:
- Get the Atlassian Cloud ID using
mcp_atlassian-mcp_getAccessibleAtlassianResources - Get current user info using
mcp_atlassian-mcp_atlassianUserInfo - Search for issues assigned to current user using the search tools (activate with
activate_search_tools_for_jira_and_confluence) - Present tickets in a clear table format
Output format:
| Key | Summary | Status | Priority |
|-----|---------|--------|----------|
| PROJ-123 | Implement login | In Progress | High |
| PROJ-124 | Fix date bug | To Do | Medium |
Create Work
Create a new Jira ticket.
Required information (prompt user if missing):
- Project key (or help user find it via
mcp_atlassian-mcp_getVisibleJiraProjects) - Summary (ticket title)
- Issue type (Story, Bug, Task, etc.)
- Component (see List Components for available options)
Mandatory fields (auto-populated):
- Requested by (BU): Default to
GLCP. User can override if needed. - Labels: Always include
created-by-github-copilot. User can add additional labels.
Optional information:
- Description
- Priority
- Assignee
- Additional labels
Steps:
- Get Cloud ID if not cached
- Gather required fields from user
- If issue type unknown, fetch available types via issue metadata tools (activate with
activate_jira_issue_management_tools) - Check user preferences file for last-used component (see User Preferences)
- If no component provided and preference exists, suggest it; otherwise prompt user
- Create issue using
mcp_atlassian-mcp_createJiraIssuewithadditional_fields:
What ships with it
1 file 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.
- 12d ago First seen · 378 lines · 151 tokens per session scan A 93a7880776a2
jira-workflow is a skill published in the GitHub repository mvilrokx/claude-skills (2 stars, last pushed 7mo ago), licensed MIT. It adds 151 tokens to every session and 2,673 once invoked, about $0.0008 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.