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 grandcamel/JIRA-Assistant-Skills --skill jira-searchgit clone --depth 1 https://github.com/grandcamel/JIRA-Assistant-SkillsWrote 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/grandcamel/jira-assistant-skills/jira-search)<a href="https://agentmods.dev/skills/grandcamel/jira-assistant-skills/jira-search"><img src="https://agentmods.dev/badge/skills/grandcamel/jira-assistant-skills/jira-search/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/grandcamel/jira-assistant-skills/jira-search"><img src="https://agentmods.dev/badge/skills/grandcamel/jira-assistant-skills/jira-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Excessive Agency · line 203 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 205 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00042 | $0.03435 |
| Opus 5 | $0.00021 | $0.01717 |
| Sonnet 5 | $0.00008 | $0.00687 |
| Haiku 4.5 | $0.00004 | $0.00344 |
Grade A, and why
jira-search-jql 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 13d 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
1 near-identical copy found in the catalogue:
- jira-search-jql — 97% identical, 26 lines differ
How it starts
The opening of the file, as written. The whole thing — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jira-search
Query and discovery operations for JIRA issues using JQL (JIRA Query Language).
Risk Levels
| Operation | Risk | Notes |
|---|---|---|
| Query/search | - |
Read-only |
| Validate JQL | - |
Read-only |
| Export results | - |
Read-only (local file) |
| List filters | - |
Read-only |
| Create filter | - |
Easily reversible (can delete) |
| Update filter | ! |
Can be reverted |
| Share filter | ! |
Can be unshared |
| Delete filter | !! |
Filter lost, but can recreate |
| Bulk update | !! |
Use --dry-run first; changes reversible but tedious |
Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible
When to use this skill
Perfect for:
- Search by criteria: "Find all bugs assigned to me in the current sprint"
- Reporting: Export sprint results or metrics to CSV/JSON
- Bulk operations: Update labels, priority, or assignee on 50+ issues at once
- Automation: Create saved filters for monitoring or dashboards
Not ideal for:
- Single issue operations - Use jira-issue skill
- Workflow transitions on many issues - Use jira-lifecycle skill
- Complex issue relationships - Use jira-relationships skill
- Sprint/board management - Use jira-agile skill
Quick Start
# Find your open issues
jira-as search query "assignee = currentUser() AND status != Done"
# Find bugs in a project
jira-as search query "project = PROJ AND type = Bug AND status = Open"
# Export results to CSV
jira-as search export "project = PROJ" --output report.csv
# Save a filter for reuse
jira-as search filter create -n "My Bugs" -j "type = Bug AND assignee = currentUser()" -f
For detailed setup, see docs/QUICK_START.md.
Available Commands
IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.
| Command | Purpose | Example |
|---|---|---|
jira-as search query |
Execute JQL queries | jira-as search query "project = PROJ" |
jira-as search export |
Export to CSV/JSON | jira-as search export "JQL" -o report.csv |
jira-as search validate |
Check JQL syntax | jira-as search validate "your query" |
jira-as search build |
Build JQL from clauses | jira-as search build --clause "project = PROJ" --clause "status = Open" |
jira-as search bulk-update |
Bulk update issues from search | jira-as search bulk-update "JQL" --add-labels bug --dry-run |
jira-as search suggest |
Get field value suggestions | jira-as search suggest --field status --no-cache |
jira-as search fields |
List available JQL fields | jira-as search fields --custom-only |
jira-as search functions |
List available JQL functions | jira-as search functions --with-examples |
jira-as search filter list |
List saved filters | jira-as search filter list --favourites |
jira-as search filter create |
Save a reusable filter | jira-as search filter create --name "Name" --jql "JQL" |
jira-as search filter update |
Update an existing filter | jira-as search filter update 10042 --name "New Name" |
jira-as search filter run |
Run a saved filter | jira-as search filter run --id 10042 |
jira-as search filter favourite |
Toggle favourite status | jira-as search filter favourite 10042 --add |
jira-as search filter share |
Share filter with users/groups | jira-as search filter share 10042 --project PROJ |
jira-as search filter delete |
Delete a saved filter | jira-as search filter delete 10042 --yes |
What ships with it
10 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.
- assets/ERROR_SOLUTIONS.json 6.3 KB
- assets/QUICK_REFERENCE.txt 2.0 KB
- assets/SCRIPT_SELECTOR.json 5.2 KB
- assets/templates/jql_templates.json 1.6 KB
- docs/QUICK_START.md 3.6 KB
- docs/SCRIPT_REFERENCE.md 7.0 KB
- references/BEST_PRACTICES.md 32 KB
- references/jql_reference.md 3.5 KB
- references/search_examples.md 2.9 KB
- references/TROUBLESHOOTING.md 8.1 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.
- 13d ago First seen · 324 lines · 42 tokens per session scan A 44d3d0d42e98
jira-search-jql is a skill published in the GitHub repository grandcamel/JIRA-Assistant-Skills (46 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 3,435 once invoked, about $0.0002 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
c-jira
Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.
reality-strategy
Change a blocked real-life or organisational situation by recovering the original result, reconstructing real participants and flows, investigating the sustaining cause, mapping stakeholders and practical power, then altering defaults, burdens, incentives, coalitions, information flow, decision rights or action…
mk:jira
Routing skill — recommends the correct mk:jira- leaf for any Jira task. Triggers: 'jira', 'jira ticket', ambiguous Jira intent. NOT an executor — every actual operation forks via a leaf skill.
Jira QA Workflows
Run QA work in Jira like a professional, bug lifecycle and triage, JQL queries for testers, quality dashboards, sprint QA rituals, and REST API automation for bulk bug operations and reporting.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
python-logging-best-practices
Python logging with loguru, structlog, and orjson. TRIGGERS - loguru, structlog, structured logging.