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 skyfox675/agents-skills --skill jira-issue-fieldsgit clone --depth 1 https://github.com/skyfox675/agents-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/skyfox675/agents-skills/jira-issue-fields)<a href="https://agentmods.dev/skills/skyfox675/agents-skills/jira-issue-fields"><img src="https://agentmods.dev/badge/skills/skyfox675/agents-skills/jira-issue-fields/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/skyfox675/agents-skills/jira-issue-fields"><img src="https://agentmods.dev/badge/skills/skyfox675/agents-skills/jira-issue-fields.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.00211 | $0.05388 |
| Opus 5 | $0.00105 | $0.02694 |
| Sonnet 5 | $0.00042 | $0.01078 |
| Haiku 4.5 | $0.00021 | $0.00539 |
Grade A, and why
jira-issue-fields 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 6d 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Control Fields (Jira)
A small set of Jira fields and labels forms the persistent, auditable control plane between human operators and orchestrating agents. Fields and labels survive across sessions, are visible to every concurrent operator, and are machine-readable in pre-dispatch JQL filters — properties that chat instructions and issue comments do not have. This skill defines the full taxonomy: what each field/label means, who sets it, who consumes it, and the resolution rules when signals conflict.
All Jira reads and writes go through the Atlassian MCP server (the official
Atlassian Remote MCP). Operations are referenced below by their canonical logical
names (getJiraIssue, editJiraIssue, searchJiraIssuesUsingJql, etc.); the exact
tool names depend on the connected server. Adopters without the Atlassian MCP can
substitute the Jira REST v3 API or a Jira CLI for the same operations — the protocol
is identical, only the call surface changes. (Stated once here; assumed everywhere
below.)
Companion skills: issue selection and the dispatch brief live in the
dispatching-subagents skill; the claim/lock/release protocol behind agent-claimed
lives in the jira-issue-locking skill; the recon/triage and groomed-body protocol lives in
the jira-issue-filing skill; the slot loop that reads these fields every round lives in the
orchestrating-slots skill; PR-side mechanics behind do-not-rebase live in the
driving-prs-to-merge skill.
Project bindings
Adopting projects define these values in their own CLAUDE.md. Refer to them by placeholder everywhere below.
| Binding | Meaning | Example |
|---|---|---|
<workhorse-model> |
Default model for all code-writing dispatches | sonnet |
<cheap-model> |
Model for narrow mechanical tasks only — deliberately has NO label | haiku |
<premium-models> |
Operator-gated high-attention models (one label each) | opus, fable |
<jira-project-key> |
Project key for JQL project = clauses and issue keys |
PROJ |
<jira-site> / cloudId |
The Jira site/cloud the MCP is connected to | resolve dynamically |
<jira-done-status> |
Workflow status that closes an issue | Done |
<jira-inprogress-status> |
In-flight status set when work starts | In Progress |
<jira-ready-status> |
Status (or label fallback) marking a groomed, dispatchable issue | Ready / triage-ready-to-dispatch |
<integration-branch> |
Branch PRs target (affects close-on-merge, see jira-issue-locking) | dev |
<auto-rebase-automation> |
Whatever workflow/bot rebases open PRs onto <integration-branch> |
a scheduled auto-rebase workflow |
<operator-logins> |
Operators running orchestrators concurrently — assignees set by accountId, resolved via lookupJiraAccountId; current user via atlassianUserInfo |
resolve dynamically |
<lock-comment-format> |
Parseable lock-comment marker paired with agent-claimed — full spec in jira-issue-locking |
a claude-lock: ... line in a comment |
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.
- 6d ago First seen · 351 lines · 211 tokens per session scan A 03519f8308af
jira-issue-fields is a skill published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 9d ago), licensed MIT. It adds 211 tokens to every session and 5,388 once invoked, about $0.0011 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-09-03.
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.
remove
Remove a deployed framework or addon from the current workspace.