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/alexgvozden/claude-pluginWrote 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/commands/alexgvozden/claude-plugin/create-jira-content)<a href="https://agentmods.dev/commands/alexgvozden/claude-plugin/create-jira-content"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/create-jira-content.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.00016 | $0.04447 |
| Opus 5 | $0.00008 | $0.02224 |
| Sonnet 5 | $0.00003 | $0.00889 |
| Haiku 4.5 | $0.00002 | $0.00445 |
Grade A, and why
create-jira-content 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 — 637 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create JIRA Content from Planning Documents
This command generates structured JIRA ticket content from planning markdown files. It supports both:
- Feature Planning: Tasks/User Stories from
/plan-featuredocuments - Bug Fix Planning: Bug tickets from
/plan-bugfixdocuments
Required Parameter
Planning Document Path: You MUST provide the path to the planning markdown file.
Example usage:
# For features (planning/ folder)
/create-jira-content planning/my-feature.md
# For bug fixes (planning/bugs/ folder)
/create-jira-content planning/bugs/KT-4313-fix-employee-data.md
Instructions
1. Validate Input
Check if parameter is provided:
- If NO path provided: Respond with error message and EXIT
- If path provided: Continue to next step
Error Message:
Error: Planning file path is required
Usage: /create-jira-content <path-to-planning-file>
Examples:
/create-jira-content planning/my-feature.md
/create-jira-content planning/bugs/KT-4313-fix-employee-data.md
Please provide the path to your planning markdown file.
2. Read and Validate Planning Document
Read the planning file:
- Use Read tool to load the markdown file
- If file doesn't exist: Show error and EXIT
Error Message for Missing File:
Error: Planning file not found
File: [provided path]
Please check:
1. The file path is correct
2. The file exists in the planning/ or planning/bugs/ directory
3. You've created a planning document using /plan-feature or /plan-bugfix
Available planning files:
[List files found in planning/ and planning/bugs/ directories]
2.5. Detect Document Type
Determine if this is a Feature or Bug Fix document:
-
Bug Fix Document (from
/plan-bugfix):- Located in
planning/bugs/folder, OR - Contains "## Bug:" or "### Bug Summary" or "### Root Cause Analysis" sections
- Located in
-
Feature Document (from
/plan-feature):- Located in
planning/folder (not in bugs/), OR - Contains "## Overview" or "## Requirements" or "## Technical Design" sections
- Located in
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 · 637 lines · 16 tokens per session scan A b9488c5617d4
create-jira-content is a command published in the GitHub repository alexgvozden/claude-plugin (11 stars, last pushed 9mo ago), licensed MIT. It adds 16 tokens to every session and 4,447 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.