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 agentmods add skills/openshift/ols/make-jira-from-specnpx skills add openshift/ols --skill make-jira-from-specgit clone --depth 1 https://github.com/openshift/olsWrote 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/openshift/ols/make-jira-from-spec)<a href="https://agentmods.dev/skills/openshift/ols/make-jira-from-spec"><img src="https://agentmods.dev/badge/skills/openshift/ols/make-jira-from-spec.svg" alt="Measured on agentmods" 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 | $0.00107 | $0.05031 |
| Opus 5 | $0.00053 | $0.02516 |
| Sonnet 5 | $0.00021 | $0.01006 |
| Haiku 4.5 | $0.00011 | $0.00503 |
Grade A, and why
make-jira-from-spec 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 today.
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 — 649 lines — stays where its author put it; the contents beside it link to each section on GitHub.
make-jira-from-spec
Turn spec changes into Jira work items. Reads the .ai/spec/
changes from the current session or a PR, brainstorms the
decomposition, creates or updates Epics and Stories, then
estimates and risk-assesses every item.
Defaults
| Setting | Value |
|---|---|
| Project key | OLS |
| Cloud ID | redhat.atlassian.net |
| Content format | markdown |
| SP field | customfield_10028 |
| Risk Score field | customfield_10976 |
| Epic Size field | customfield_10795 |
| Max story points | 5 (split if above) |
Invocation
/make-jira-from-spec
/make-jira-from-spec https://github.com/org/repo/pull/123
/make-jira-from-spec https://github.com/org/repo1/pull/10 https://github.com/org/repo2/pull/20
/make-jira-from-spec OLS-1234
Arguments (all optional, can be combined):
- PR URL(s) — one or more PR URLs to fetch spec diffs from (spec changes often span multiple repos)
- Jira key — existing Epic or Story to update
Step 1: Gather Spec Changes
Resolve the spec changes using this priority:
1a. PR URL(s) provided
Fetch the diff from each PR with gh pr diff <URL>. Filter
to files under .ai/spec/. When multiple PR URLs are given,
collect spec diffs from all of them — spec changes often
span multiple repos. Read the full content of each changed
spec file.
Overlap detection. If the same spec file appears in
multiple PR diffs, fetch the head revision from each PR
(gh pr view <URL> --json headRefOid) and compare the
file at each head. Flag the overlap to the user before
proceeding — do not silently pick one version. Ask which
PR's version to use as the baseline for decomposition.
1b. Session context (no PR URLs)
Find spec files changed in the current session across all repos in the workspace:
# From the workspace root
for repo in */; do
git -C "$repo" diff HEAD -- .ai/spec/ 2>/dev/null
done
Also check for untracked new spec files:
for repo in */; do
git -C "$repo" diff --cached -- .ai/spec/ 2>/dev/null
git -C "$repo" ls-files --others --exclude-standard .ai/spec/ 2>/dev/null
done
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.
- today Changed · +1 lines acde1dad954f
- 4d ago First seen · 648 lines · 107 tokens per session scan A e82c6a61bbab
make-jira-from-spec is a skill published in the GitHub repository openshift/ols (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 107 tokens to every session and 5,031 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…