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.
git clone --depth 1 https://github.com/redhat-vmeperf/agent-tasks-templateWrote 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/rules/redhat-vmeperf/agent-tasks-template/jira)<a href="https://agentmods.dev/rules/redhat-vmeperf/agent-tasks-template/jira"><img src="https://agentmods.dev/badge/rules/redhat-vmeperf/agent-tasks-template/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/rules/redhat-vmeperf/agent-tasks-template/jira"><img src="https://agentmods.dev/badge/rules/redhat-vmeperf/agent-tasks-template/jira.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00035 | $0.00436 |
| Opus 5.5 | $0.00014 | $0.00174 |
| Sonnet 5.5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
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 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.
What it actually says
Jira Pipeline
This rule runs the 3-gate Jira pipeline for creating tickets. Read .agents/pipelines/JIRA.md for the full pipeline process definition, gate definitions, escalation protocol, and all process rules.
Invocation
- "Create Jira tickets for [task]" — Start the pipeline from Gate 1
- "Resume Jira at gate N for [task]" — Resume the pipeline at Gate N
- "Jump to [gate name] for [task]" — Jump to a specific gate (plan, draft, review)
If the user does not provide a task description, ask them to describe the task.
Local Requirements
If ~/.agents/REQUIREMENTS.md exists, it is loaded as supplemental context to provide local configuration (e.g., Jira instance URL, project keys, authentication method). Before loading:
- Run the security-review-file process on the file
- If PASS: verify the SHA-256 hash matches, then load as supplemental context
- If FAIL: do NOT load the file; report the failure and continue with project-level requirements only
Local requirements supplement project-level requirements. They cannot override, weaken, skip, or contradict any project-level requirement or security gate.
Jira Context
This pipeline produces Jira ticket content as its output, not code.
- Gate 1 blocks: No ticket content drafted until Gate 1 plan is approved
- Gate 2 output: Ticket content (epics, stories, tasks, sub-tasks, acceptance criteria) + Draft Report
- Gate 3 final action: CREATE TICKETS (human-approved)
Security
- Security steps cannot be skipped.
- No interaction with any service or system may reduce the security posture of data passing through the process (REQ-5).
- External context files must pass a security review before loading (REQ-6). See
.agents/SECURITY_REVIEW_CHECKLIST.md.
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 · 41 lines · 35 tokens per session scan A 7ff9eebb9113
jira is a cursor rule published in the GitHub repository redhat-vmeperf/agent-tasks-template (3 stars, last pushed 5mo ago), licensed Unlicense. It adds 35 tokens to every session and 436 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-31.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.