Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/anhtester/antigravity-testing-kitnpx agentmods add skills/anhtester/antigravity-testing-kit/jira_integrationWrote 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/anhtester/antigravity-testing-kit/jira_integration)<a href="https://agentmods.dev/skills/anhtester/antigravity-testing-kit/jira_integration"><img src="https://agentmods.dev/badge/skills/anhtester/antigravity-testing-kit/jira_integration/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/anhtester/antigravity-testing-kit/jira_integration"><img src="https://agentmods.dev/badge/skills/anhtester/antigravity-testing-kit/jira_integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 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 59 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 64 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 175 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 74 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.
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.00034 | $0.01461 |
| Opus 5.5 | $0.00014 | $0.00584 |
| Sonnet 5.5 | $0.00007 | $0.00292 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
jira_integration 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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- jira_integration — 100% identical, 0 lines differ
- skills-jira-integration — 94% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira & Xray Integration Skill
Mô tả
Skill này cung cấp khả năng tích hợp giữa Antigravity Testing Kit với hệ thống Jira và Xray để:
- Lấy Requirements/User Stories từ Jira → chuyển thành tài liệu yêu cầu chuẩn
- Xác thực Xray (Cloud hoặc Server/Data Center)
- Đẩy kết quả test (Playwright, JUnit, Allure) lên Xray Test Management
Khi nào sử dụng
Agent sử dụng skill này khi user yêu cầu:
- Lấy requirement / user story từ Jira
- Kết nối / test connection đến Jira API
- Đẩy kết quả test lên Xray
- Import test results lên Jira
- Xác thực Xray token
- Tích hợp CI/CD với Jira
Trigger keywords:
- "fetch jira", "lấy requirement từ jira", "get jira ticket"
- "import xray", "đẩy kết quả lên xray", "push test results"
- "test jira connection", "kiểm tra kết nối jira"
Cấu trúc Scripts
scripts/integrations/
├── jira/
│ ├── jira_fetcher.js # Lấy Requirement/User Story từ Jira
│ ├── xray_auth.js # Xác thực và lấy Token Xray
│ ├── xray_importer.js # Import kết quả test lên Xray
│ └── utils.js # Hàm utility dùng chung
└── package.json # Dependencies (axios, dotenv)
Điều kiện tiên quyết (Prerequisites)
1. Cài đặt dependencies
cd scripts/integrations
npm install
2. Cấu hình .env
Copy .env.example thành .env ở thư mục gốc project:
cp .env.example .env
Điền các thông tin bắt buộc:
| Biến | Mô tả | Bắt buộc |
|---|---|---|
JIRA_BASE_URL |
URL Jira instance (VD: https://domain.atlassian.net) |
✅ |
JIRA_EMAIL |
Email tài khoản Jira (Cloud) | ✅ (Cloud) |
JIRA_API_TOKEN |
API Token (Cloud) | ✅ (Cloud) |
JIRA_PAT |
Personal Access Token (Server/DC) | ✅ (Server) |
JIRA_PROJECT_KEY |
Project key mặc định | Khuyến nghị |
XRAY_PLATFORM |
cloud hoặc server |
Mặc định: cloud |
XRAY_CLIENT_ID |
Xray API Client ID | Khi dùng Xray Cloud |
XRAY_CLIENT_SECRET |
Xray API Client Secret | Khi dùng Xray Cloud |
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.
- 1mo ago First seen · 176 lines · 34 tokens per session scan A 04c8717ed063
jira_integration is a skill published in the GitHub repository anhtester/antigravity-testing-kit (147 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 1,461 once invoked, about $0.0001 per session on Opus 5.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
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
framework-migration-deps-upgrade
Plan incremental dependency upgrades with breaking-change analysis, migration guidance, and regression testing. Use when updating packages while controlling compatibility risk.
kanban
Use when work has several deliverables, tickets, or delegates: board, WIP 1 writer + 2 review, pull rule, Definition of Done, findings fixed or filed.
shaft-developer
Use when starting any SHAFT testing task to select exactly one lifecycle, implementation, or tool specialist before doing the work.
shaft-test-case-design
Use when designing reviewable test cases or scenarios with traceability, data, steps, expected results, techniques, priorities, and boundary coverage.
shaft-accessibility-testing
Use when testing web or mobile accessibility for WCAG conformance, keyboard and focus behavior, semantics, errors, or user impact.