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 event4u-app/agent-config --skill jira-integrationgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/jira-integration)<a href="https://agentmods.dev/skills/event4u-app/agent-config/jira-integration"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/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/event4u-app/agent-config/jira-integration"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/jira-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 178 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.00036 | $0.01309 |
| Opus 5 | $0.00018 | $0.00655 |
| Sonnet 5 | $0.00007 | $0.00262 |
| Haiku 4.5 | $0.00004 | $0.00131 |
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 9d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Skill
When to use
Use this skill when:
- Reading a Jira ticket for context (bug reports, feature requests)
- Creating new Jira issues from discovered bugs or planned work
- Transitioning ticket status (e.g., "In Progress" → "In Review")
- Writing JQL queries to find related issues
- Linking branches or PRs to Jira tickets
Do NOT use when:
- GitHub Issues (use
github-apitool directly) - Linear or other issue trackers
Procedure: Work with Jira
- Identify action — Search, read, create, update, or transition a ticket?
- Use the correct endpoint — See API table below.
- Execute — Make the API call with required fields.
- Verify — Confirm the response contains expected data or the ticket was updated.
| Tool | Purpose |
|---|---|
jira-integration (GET /search/jql) |
Search issues with JQL |
jira-integration (GET /issue/{key}) |
Read a specific ticket |
jira-integration (POST /issue) |
Create a new ticket |
jira-integration (PUT /issue/{key}) |
Update a ticket |
jira-integration (GET /issue/{key}/transitions) |
Get available status transitions |
jira-integration (POST /issue/{key}/transitions) |
Transition ticket status |
jira-integration (POST /issue/{key}/comment) |
Add a comment |
jira-integration (GET /project) |
List projects |
jira-integration (GET /field) |
List available fields (check before writing JQL) |
Branch-to-ticket detection
Extract ticket IDs from branch names automatically:
feat/DEV-1234/user-notifications → DEV-1234
fix/DEV-5678/null-pointer → DEV-5678
hotfix/DEV-999/critical-fix → DEV-999
Pattern: [A-Z]+-[0-9]+ anywhere in the branch name.
Use git branch --show-current to detect, then fetch the ticket:
jira GET /issue/DEV-1234
JQL patterns
Common queries
# My open tickets
assignee = currentUser() AND status != Done ORDER BY priority DESC
# Tickets in current sprint
project = DEV AND sprint in openSprints() AND assignee = currentUser()
# Recently updated bugs
project = DEV AND type = Bug AND updated >= -7d ORDER BY updated DESC
# Tickets by component
project = DEV AND component = "Import" AND status != Done
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.
- 9d ago First seen · 188 lines · 36 tokens per session scan A 0da15511709c
jira-integration is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,309 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-09-03.
Other skills, from other repositories
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
pad
Talk to your project. Natural-language project management — create items, check status, plan work, brainstorm ideas, and more.
pm-arch
Skill "pm-arch" from wei63w/pm-manager, covering user input, outline, done when and shared workflow (all /pm- commands).
pm-discover
Skill "pm-discover" from wei63w/pm-manager, covering user input, outline and shared workflow.