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/microsoft/hve-core/jiranpx skills add microsoft/hve-core --skill jiragit clone --depth 1 https://github.com/microsoft/hve-coreWrote 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/microsoft/hve-core/jira)<a href="https://agentmods.dev/skills/microsoft/hve-core/jira"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/jira.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.00070 | $0.03771 |
| Opus 5 | $0.00035 | $0.01886 |
| Sonnet 5 | $0.00014 | $0.00754 |
| Haiku 4.5 | $0.00007 | $0.00377 |
Grade A, and why
jira 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 4d 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Skill
Overview
This skill provides a Python CLI for common Jira REST API workflows:
- Search with JQL
- Get issue details
- Create and update issues with JSON payloads
- Transition issues by name or ID
- Add comments and list existing comments
- Discover issue types and required fields for creation
The skill supports Jira Cloud with email plus API token authentication and Jira Server or Data Center with a personal access token.
Use --fields on read commands by default to keep output concise. The script supports dot-notation such as fields.status.name and prints tab-separated output for lists.
Prerequisites
Set the required environment variables before running the script.
| Platform | Runtime |
|---|---|
| Cross-platform | Python 3.11+ |
Authentication Variables
| Variable | When required | Purpose |
|---|---|---|
JIRA_BASE_URL |
Always | Jira base URL, for example https://company.atlassian.net |
JIRA_USER_EMAIL |
Jira Cloud | Account email used for basic authentication |
JIRA_API_TOKEN |
Jira Cloud | API token paired with the Jira Cloud email |
JIRA_PAT |
Jira Server or Data Center | Personal access token used for bearer authentication |
JIRA_CLOUD_TOKEN_MODE |
Jira Cloud optional | unscoped (default) or scoped |
JIRA_CLOUD_ID |
Scoped Jira Cloud token | Atlassian Cloud resource identifier |
Authentication is selected automatically:
- If
JIRA_PATis set, the script uses bearer authentication for Jira Server or Data Center. - Otherwise, the script expects
JIRA_USER_EMAILandJIRA_API_TOKENfor Jira Cloud. - Scoped Cloud mode routes only to
https://api.atlassian.com/ex/jira/{cloudId}; mixed Cloud and Data Center credentials fail closed.
What ships with it
46 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.
- pyproject.toml 680 B
- references/jql-reference.md 3.4 KB
- scripts/jira.py 40 KB runs code
- SECURITY.md 22 KB
- tests/conftest.py 4.3 KB runs code
- tests/corpus/0_error_payload 32 B
- tests/corpus/0_json_error 32 B
- tests/corpus/0_large 2.0 KB
- tests/corpus/0_null_bytes 14 B
- tests/corpus/0_unicode_stress 13 B
- tests/corpus/1_empty 1 B
- tests/corpus/1_issue_key 9 B
- tests/corpus/1_long_key 24 B
- tests/corpus/1_null_bytes 10 B
- tests/corpus/1_unicode_key 11 B
- tests/corpus/1_valid_key 9 B
- tests/corpus/2_deeply_nested 604 B
- tests/corpus/2_empty 1 B
- tests/corpus/2_field_path 15 B
- tests/corpus/2_large_json 2.0 KB
- tests/corpus/2_nested_json 30 B
- tests/corpus/2_unicode_fields 26 B
- tests/corpus/3_comma_separated 21 B
- tests/corpus/3_empty 1 B
- tests/corpus/3_fields_csv 19 B
- tests/corpus/3_large 890 B
- tests/corpus/3_null_bytes 11 B
- tests/corpus/3_unicode_fields 16 B
- tests/corpus/4_deeply_nested 304 B
- tests/corpus/4_empty 1 B
- tests/corpus/4_json_array 10 B
- tests/corpus/4_json_object 18 B
- tests/corpus/4_malformed_json 9 B
- tests/corpus/4_trailing_garbage 21 B
- tests/corpus/4_unicode_json 17 B
- tests/corpus/c45a54a39a931a07d4c7bccd0ca46a538e210cf3 20 B
- tests/corpus/README.md 1.3 KB
- tests/fuzz_harness.py 5.5 KB runs code
- tests/test_constants.py 1.4 KB runs code
- tests/test_jira_audit.py 6.1 KB runs code
- tests/test_jira_commands.py 9.0 KB runs code
- tests/test_jira_coverage.py 7.1 KB runs code
- tests/test_jira_helpers.py 13 KB runs code
- tests/test_jira_main.py 5.9 KB runs code
- tests/test_jira_transport.py 17 KB runs code
- uv.lock 57 KB
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.
- 4d ago First seen · 310 lines · 70 tokens per session scan A b1dc295e5f41
jira is a skill published in the GitHub repository microsoft/hve-core (1,422 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 3,771 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…