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/update-jira-ticket)<a href="https://agentmods.dev/commands/alexgvozden/claude-plugin/update-jira-ticket"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/update-jira-ticket/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/commands/alexgvozden/claude-plugin/update-jira-ticket"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/update-jira-ticket.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.00016 | $0.02730 |
| Opus 5 | $0.00008 | $0.01365 |
| Sonnet 5 | $0.00003 | $0.00546 |
| Haiku 4.5 | $0.00002 | $0.00273 |
Grade A, and why
update-jira-ticket 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 10d 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Jira Ticket from Content File
This command updates an existing Jira ticket with content from a JIRA content markdown file. It validates the filename format, reads the content, and pushes the update to Jira via Atlassian MCP.
Usage
Single parameter format:
/update-jira-ticket jira/KT-4054-ticket-name-with-dashes/KT-4054-ticket-name-with-dashes.md
Instructions
Progress Reporting: Show concise progress messages for each step (e.g., "Validating filename format... ✅") without detailed explanations unless errors occur.
1. Validate Input Parameter
Check if parameter is provided:
- If NO parameter provided: Show error message and EXIT
- If parameter provided: Continue to next step
Error Message for Missing Parameter:
Error: JIRA content file path is required
Usage: /update-jira-ticket <jira-content-file-path>
Example:
/update-jira-ticket jira/KT-4054-ticket-name-with-dashes/KT-4054-ticket-name-with-dashes.md
Please provide the path to your JIRA content markdown file.
2. Validate Filename Format
Check filename format:
- Must be in format:
[ticket-id]-ticket-name-with-dashes.md - Must be in
jira/[ticket-id]-ticket-name-with-dashes/directory structure - Ticket ID must match pattern:
^[A-Z]+-\d+(e.g., KT-4054, KPT-2321) - File must be named exactly:
[ticket-id]-ticket-name-with-dashes.md
Error Message for Invalid Filename:
Error: Invalid JIRA content file format
File: [provided path]
Expected format: jira/[ticket-id]-ticket-name-with-dashes/[ticket-id]-ticket-name-with-dashes.md
Examples:
jira/KT-4054-ticket-name-with-dashes/KT-4054-ticket-name-with-dashes.md ✅
jira/KPT-2321-implementation-notes/KPT-2321-implementation-notes.md ✅
planning/KT-4054-my-feature.md ❌ (wrong directory)
jira/KT-4054-ticket-name/KT-4054-different-name.md ❌ (filename mismatch)
jira/invalid-ticket-name/invalid-ticket-name.md ❌ (invalid ticket ID format)
Please ensure:
1. File is in jira/ directory
2. Folder name matches pattern: [ticket-id]-ticket-name-with-dashes
3. File name matches pattern: [ticket-id]-ticket-name-with-dashes.md
4. Ticket ID format: [PROJECT]-[NUMBER] (e.g., KT-4054)
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.
- 10d ago First seen · 351 lines · 16 tokens per session scan A d5a1ce3d8470
update-jira-ticket 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 2,730 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.