HVE Core is a collection of agents, prompts, coding instructions, and skills for building repeatable software-development workflows with GitHub Copilot. It is intended for individuals and teams that want structured AI-assisted research, planning, implementation, and review, while the catalogue entries provide many of its reusable workflow components.
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 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/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/microsoft/hve-core/jira"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/jira.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 9 findings, up to high
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 →
- high Privilege Escalation · line 27 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 46 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 54 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Rogue Agent · line 64 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Prompt Injection · line 95 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Rogue Agent · line 117 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 148 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Prompt Injection · line 302 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 306 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00070 | $0.04046 |
| Opus 5.5 | $0.00028 | $0.01618 |
| Sonnet 5.5 | $0.00014 | $0.00809 |
| Haiku 4.5 | $0.00007 | $0.00405 |
Grade B, and why
jira scanned grade B with 1 finding 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 2mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
1. On POSIX, create the file with owner-only permissions by running `umask 077; touch ~/.jira.env; chmod 0600 ~/.jira.env`. On Windows, create it under the user's profile and apply a user-only ACL. Fill in non-secret val How it starts
The opening of the file, as written. The whole thing — 316 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 44 KB runs code
- SECURITY.md 24 KB
- tests/conftest.py 4.4 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 20 KB runs code
- tests/test_jira_main.py 7.7 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.
- 2mo ago Changed · +6 lines scan A → B 44a9e23b1080
- 2mo 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,606 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 4,046 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
jira compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| jiramicrosoft/hve-core | Skill | 1.6k | today | MIT | B | 70 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | yesterday | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 4d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |