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-filinggit 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-filing)<a href="https://agentmods.dev/skills/skyfox675/agents-skills/jira-issue-filing"><img src="https://agentmods.dev/badge/skills/skyfox675/agents-skills/jira-issue-filing/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-filing"><img src="https://agentmods.dev/badge/skills/skyfox675/agents-skills/jira-issue-filing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 3 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 66 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00222 | $0.05235 |
| Opus 5 | $0.00111 | $0.02618 |
| Sonnet 5 | $0.00044 | $0.01047 |
| Haiku 4.5 | $0.00022 | $0.00524 |
Grade A, and why
jira-issue-filing 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.
How it starts
The opening of the file, as written. The whole thing — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Filing Jira Issues That Agents Can Ship
Issues filed here feed the multi-agent pipeline (claimed per jira-issue-locking, dispatched per dispatching-subagents, scheduled per orchestrating-slots, merged per driving-prs-to-merge; fields/labels per jira-issue-fields). This skill covers both ends of intake: writing groomed issues, and recon-triaging stubs.
All Jira reads and writes go through the Atlassian MCP server (the official
Atlassian Remote MCP); operations are named by their canonical tool
(createJiraIssue, getJiraIssue, editJiraIssue, searchJiraIssuesUsingJql,
transitionJiraIssue, addCommentToJiraIssue) — 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.
Project bindings
Define these once in the adopting project's CLAUDE.md, alongside the sibling skills' shared bindings (integration branch, worktree convention, toolchain bootstrap, CI gate names, bot reviewers, operator accountIds). The body refers to them by placeholder; example values are illustrations, not requirements.
| Binding | Meaning | Example |
|---|---|---|
<jira-project-key> |
project key targeted by createJiraIssue / JQL |
PROJ |
<jira-site> |
site/cloudId the MCP operates against | acme.atlassian.net |
<issue-types> |
exactly-one issue type per ticket | Bug, Story, Task |
<priority-field> |
exactly-one native Priority value | Highest…Lowest |
<jira-ready-status> |
workflow status meaning ready-to-dispatch | Ready |
<jira-inprogress-status> |
workflow status meaning active work | In Progress |
<jira-blocked-status> / <jira-needs-input-status> |
terminal triage statuses (label fallback below) | Blocked / Needs Input |
<jira-done-status> |
terminal completed status | Done |
<security-label> |
flag for authn/authz/data-isolation/OWASP-class issues | security |
<lane-labels> |
shared-surface vs isolated work (hyphenated; no spaces) | lane-plumbing, lane-leaf |
<component-labels> |
component/subsystem label or Component | subsystem-auth |
<triage-labels> |
terminal triage states, label fallback when workflow is locked | triage-ready-to-dispatch, triage-needs-spec-input, triage-blocked |
<claim-label> / <hold-label> |
active-work lock (jira-issue-locking) / operator hold (jira-issue-fields); neither applied at filing | agent-claimed / do-not-dispatch |
<breaking-change-labels> |
CI breaking-change acknowledgment gates, if any | db-breaking-change-acknowledged / api-breaking-change-acknowledged |
<traceability-scheme> |
requirement-ID format + doc location, if formal traceability exists | REQ-<PREFIX>-<N> in docs/specs/ |
<shared-surfaces> |
enumerated contention-prone files defining the plumbing lane | DB schema, new migrations, API schema, design tokens, shared-types package, root manifest/lockfile |
<crown-jewel-invariant> |
hardest invariant; mentioning it auto-escalates to Highest | "tenant isolation" |
<subsystem-tiers> |
security-critical (auto-Highest) / core (partial → High) / deferred (auto-stall without logged decisions) | auth/payments vs core feature modules vs deferred/experimental areas… |
<decision-records> |
where architectural decisions for deferred areas are logged | docs/specs/_subsystems/ |
<design-source> |
UI source of truth a UI spec must anchor to | design-system/ folder |
<cheap-model> / <default-model> |
recon model tier / escalation tier | haiku / sonnet |
What ships with it
2 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 · 398 lines · 222 tokens per session scan A 49a265141f60
jira-issue-filing is a skill published in the GitHub repository skyfox675/agents-skills (11 stars, last pushed 12d ago), licensed MIT. It adds 222 tokens to every session and 5,235 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.
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.