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 redhat-vmeperf/agent-tasks-template --skill jiragit 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/skills/redhat-vmeperf/agent-tasks-template/jira)<a href="https://agentmods.dev/skills/redhat-vmeperf/agent-tasks-template/jira"><img src="https://agentmods.dev/badge/skills/redhat-vmeperf/agent-tasks-template/jira.svg" alt="Measured on agentmods" 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.00032 | $0.00686 |
| Opus 5 | $0.00016 | $0.00343 |
| Sonnet 5 | $0.00006 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00069 |
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Skill
This skill 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.
Arguments:
/jira <task description>— Start the pipeline from Gate 1/jira resume:<N> <task>— Resume the pipeline at Gate N (e.g., after revisions)/jira gate:<name>— Jump to a specific gate (plan, draft, review)
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 (e.g., local requirements) must pass a security review before loading (REQ-6). See
.agents/SECURITY_REVIEW_CHECKLIST.md.
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:
- Invoke
/security-review-fileon 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 to the human 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 skill 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)
Jira Concepts for Gate Agents
- Epic: A large body of work decomposed into stories. Maps to a high-level feature or initiative.
- Story: A user-facing unit of value. Written as "As a [role], I want [goal], so that [benefit]."
- Task: A technical unit of work that does not directly deliver user value (e.g., infrastructure, refactoring, tooling).
- Sub-task: A breakdown of a story or task into implementable steps.
- Acceptance Criteria: Conditions that must be true for a story to be considered complete. Written as testable statements.
- Labels / Components: Organizational metadata. Use labels for cross-cutting concerns and components for system boundaries.
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 · 62 lines · 32 tokens per session scan A 0e142b512273
jira is a skill published in the GitHub repository redhat-vmeperf/agent-tasks-template (3 stars, last pushed 4mo ago), licensed Unlicense. It adds 32 tokens to every session and 686 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.