Borrowing it
Nothing to install: this file belongs to Contrast-Security-OSS/mcp-contrast. 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/Contrast-Security-OSS/mcp-contrast/main/.claude/skills/jira-workflow/SKILL.mdgit clone --depth 1 https://github.com/Contrast-Security-OSS/mcp-contrastWrote 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/contrast-security-oss/mcp-contrast/jira-workflow)<a href="https://agentmods.dev/skills/contrast-security-oss/mcp-contrast/jira-workflow"><img src="https://agentmods.dev/badge/skills/contrast-security-oss/mcp-contrast/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/contrast-security-oss/mcp-contrast/jira-workflow"><img src="https://agentmods.dev/badge/skills/contrast-security-oss/mcp-contrast/jira-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00098 | $0.01054 |
| Opus 5 | $0.00049 | $0.00527 |
| Sonnet 5 | $0.00020 | $0.00211 |
| Haiku 4.5 | $0.00010 | $0.00105 |
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 10d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Workflow
Beads (br) is the working issue store for this repo and Jira is the external reference. Every Jira ticket has a matching bead, and the two are kept in sync. This skill covers ticket creation, bead parity rules, and lifecycle transitions. For the broader beads workflow see the bead-workflow skill and docs/agents/issue-tracker.md.
Public repo note. This repository is public. Committed files may reference the AIML project, the Contrast MCP Server component, and the transition IDs below, all already public in this repo. Do not commit other component names, internal service or product names, or ticket content beyond what a public reader should see.
1. Create the ticket
All work on this repo files into the AIML Jira project with component Contrast MCP Server. Use the Atlassian MCP tools (load via ToolSearch if needed). Metadata and a creation example are in references/aiml.md.
- Issue type:
Storyfor features,Taskfor simple non-feature changes (refactoring, docs, bug fixes),Epicfor large multi-ticket efforts (typically managed by Product Management). - Look up an assignee with
lookupJiraAccountId, link related tickets withcreateIssueLink. - When starting work, assign the ticket to the current user (
atlassianUserInfo) and transition it to In Progress (21). - Repo label. Add a
repo:<name>Jira label for each repo the ticket touches. For work in this repo, always addrepo:mcp-contrast. Work spanning multiple repos (e.g. mcp-contrast and aiml-services) gets both labels. Set the label at creation viaadditional_fields, or add it witheditJiraIssueif the ticket already exists.
2. Keep a bead in parity (every time)
Beads is primary. A Jira ticket should not exist without a matching bead.
When a Jira ticket is created:
- Find or create the matching bead. If a bead already drove the ticket, use it. Otherwise create one per the
bead-workflowskill, matching the Jira issue type. - Prefix the bead title with the Jira key, then a colon and a space:
AIML-1304: <title>. Do not use space-dash-space. Keep the existing title text. - Set the bead
external-refto the Jira key,br update <bead> --external-ref AIML-1304. - Add a bead comment with the Jira URL so the thread records the link.
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.
- 10d ago First seen · 60 lines · 98 tokens per session scan A 44c4a88030fc
jira-workflow is a skill published in the GitHub repository Contrast-Security-OSS/mcp-contrast (23 stars, last pushed 5d ago), licensed Apache-2.0. It adds 98 tokens to every session and 1,054 once invoked, about $0.0005 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.