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 Arvo-AI/aurora --skill jiragit clone --depth 1 https://github.com/Arvo-AI/auroraWrote 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/arvo-ai/aurora/jira)<a href="https://agentmods.dev/skills/arvo-ai/aurora/jira"><img src="https://agentmods.dev/badge/skills/arvo-ai/aurora/jira.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.01429 |
| Opus 5 | $0.00010 | $0.00714 |
| Sonnet 5 | $0.00004 | $0.00286 |
| Haiku 4.5 | $0.00002 | $0.00143 |
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 8d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Integration
Overview
Jira integration for searching recent development context during Root Cause Analysis and tracking incidents afterward. Jira is a mandatory first step in any RCA investigation -- search here BEFORE infrastructure or CI/CD tools.
Jira operates in one of two modes based on user preference (jira_mode):
comment_only(default): Onlyjira_search_issues,jira_get_issue, andjira_add_commentare available.full: All six tools are available including create, update, and link.
Instructions
MANDATORY FIRST STEP -- CHANGE CONTEXT & KNOWLEDGE BASE
You MUST call Jira tools BEFORE any infrastructure or CI/CD investigation. Skipping this step is a failure of the investigation.
Your FIRST tool calls MUST be jira_search_issues.
Tools
Investigation tools (always available):
jira_search_issues(jql='...')-- Search Jira issues using JQL. Returns matching issues with key, summary, status, assignee, labels.jira_get_issue(issue_key='PROJ-123')-- Get full details of a Jira issue by key. Returns description, status, comments, linked PRs.jira_add_comment(issue_key='PROJ-123', comment='...')-- Add a comment to a Jira issue. Non-destructive operation.
Write tools (full mode only):
jira_create_issue(project_key='PROJ', summary='...', description='...', issue_type='Bug')-- Create a new Jira issue in a project.jira_update_issue(issue_key='PROJ-123', ...)-- Update fields on an existing Jira issue.jira_link_issues(inward_issue='PROJ-123', outward_issue='PROJ-456', link_type='Relates')-- Create a link between two Jira issues (Relates, Blocks, Clones, etc.).
RCA Investigation Flow
Step 1 -- Find related recent work (DO THIS IMMEDIATELY)
jira_search_issues(jql='text ~ "SERVICE" AND updated >= -7d ORDER BY updated DESC')-- Recent tickets for this servicejira_search_issues(jql='type in (Bug, Incident) AND status != Done AND updated >= -14d ORDER BY updated DESC')-- Open bugs/incidentsjira_search_issues(jql='type in (Story, Task) AND status = Done AND updated >= -3d ORDER BY updated DESC')-- Recently completed work (likely deployed)
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.
- 8d ago First seen · 116 lines · 19 tokens per session scan A 0d72be357511
jira is a skill published in the GitHub repository Arvo-AI/aurora (405 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 1,429 once invoked, about $0.0001 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
tax-lawyer-software-interfaces
MCP tool design patterns for the Tax-Lawyer Platform. Thin Satisfies wrappers (<=10 lines per handler), TaxArgs contract types, and the full tool name taxonomy for ledgerrtax MCP actions.
b00t
Identify integration points, data flow via redis, suggest how to bridge VSCode plugin to b00t jobs, and outline k0s/podman/docker-agnostic redis interface. Include how ralph should be wrapped as b00t job with redis exchange + Azure access, and call out where integration tests are required. ONLY do this analysis. Reply…
terraform-infrastructure-as-code
Comprehensive Terraform Infrastructure as Code skill covering resources, modules, state management, workspaces, providers, and advanced patterns for cloud-agnostic infrastructure deployment.
isaac-automator
Deploy and operate a cloud Isaac Workstation with Isaac Automator: provision a GPU VM running Isaac Sim, Isaac Lab, and/or Isaac Lab Arena on AWS, GCP, Azure, or Alibaba Cloud, connect to it, move data in and out, control cost with stop/start, repair, import existing deployments, and destroy. Use when the user wants a…
cloud-iam-deep
GCP/AWS/Azure cloud exploitation -- Cloud Functions, Firestore, Cloud Run, S3, MinIO, Blob Storage, SA keys.
ak-add-integration
Add a messaging platform integration to an existing Agent Kernel project. This skill guides you through adding Slack, WhatsApp, Messenger, Instagram, Telegram, Teams, or Gmail integration by generating configuration, updating dependencies, and setting up webhook handlers. Designed for users extending their agents.