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.
git 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/commands/skyfox675/agents-skills/jira-issue)<a href="https://agentmods.dev/commands/skyfox675/agents-skills/jira-issue"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/jira-issue/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/commands/skyfox675/agents-skills/jira-issue"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/jira-issue.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.00083 | $0.01168 |
| Opus 5 | $0.00042 | $0.00584 |
| Sonnet 5 | $0.00017 | $0.00234 |
| Haiku 4.5 | $0.00008 | $0.00117 |
Grade A, and why
jira-issue 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/jira-issue — file a groomed Jira issue
Arguments: $ARGUMENTS
Parse them as:
- The first token (or quoted phrase) is the breadcrumb — a UI path (
Settings > Billing > Invoice row), a route (/dashboard), a component or object name, or a file path. - Optional
model:<tier>andeffort:<level>tokens may appear anywhere in the arguments. Strip them out before reading the rest. Valid tiers/levels come from the jira-issue-fields skill's taxonomy (model:sonnet|opus|fable; effort:low|medium|high|max, adjusted to the project's bound model lineup). An unrecognized value is a typo — warn the operator and file without that label rather than inventing one. - Everything else is the description of the problem as the operator experienced it.
Example: /jira-issue "Settings > Billing > Invoice row" clicking an invoice opens a 404 model:opus effort:high
The jira-issue-filing skill is the protocol — issue anatomy, the Jira field/label taxonomy, duplicate etiquette all come from it. This command is the entry point; consult the skill before drafting. Jira reads/writes go through the Atlassian MCP (createJiraIssue, searchJiraIssuesUsingJql, getJiraIssue, editJiraIssue, …) — allowlist your server's tools in .claude/settings.json (the prefix above, mcp__atlassian__, may differ from your configured server name); adopters without the MCP can substitute the Jira REST v3 API or a Jira CLI. (Tracking work in GitHub instead? Use /gh-issue.)
Steps
-
Recon the breadcrumb. Resolve it to real code: search the repo for the component/route/object it names and capture the concrete
file:linepointers the skill's evidence section requires. Verify every pointer by reading it before citing — stale references are worse than none. If the breadcrumb matches multiple candidates, cite the strongest and list the runners-up in the issue body so the implementer doesn't re-derive them. -
Check for duplicates per the skill's etiquette:
searchJiraIssuesUsingJqlfor the key terms from the breadcrumb and description (e.g.project = <jira-project-key> AND statusCategory != Done AND text ~ "<terms>"). If a live duplicate exists, enrich it with a comment (your recon evidence) instead of forking a new issue, and report that outcome instead. If the operator passedmodel:/effort:, apply those labels to the duplicate — that instruction stands regardless of which issue carries the work.
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 · 34 lines · 83 tokens per session scan A f7c5e29bb49e
jira-issue is a command published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 8d ago), licensed MIT. It adds 83 tokens to every session and 1,168 once invoked, about $0.0004 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.