Borrowing it
Nothing to install: this file belongs to SAGAAIDEV/mcp-ahrefs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SAGAAIDEV/mcp-ahrefs/main/.claude/commands/create-jira-issue.mdgit clone --depth 1 https://github.com/SAGAAIDEV/mcp-ahrefsWrote 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/sagaaidev/mcp-ahrefs/create-jira-issue)<a href="https://agentmods.dev/commands/sagaaidev/mcp-ahrefs/create-jira-issue"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/create-jira-issue/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/sagaaidev/mcp-ahrefs/create-jira-issue"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/create-jira-issue.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.00026 | $0.01428 |
| Opus 5 | $0.00013 | $0.00714 |
| Sonnet 5 | $0.00005 | $0.00286 |
| Haiku 4.5 | $0.00003 | $0.00143 |
Grade A, and why
create-jira-issue 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I'll help you create a detailed JIRA issue by analyzing the codebase and structuring it according to team standards. Let me parse your request and gather the necessary information.
Parse Arguments
Let me extract the issue details from your request:
- Arguments provided: $ARGUMENTS
- Expected format: [TYPE] [SITE-ALIAS] "[TITLE]" "[BRIEF-DESCRIPTION]"
Accepted TYPE values:
- For new features:
feature,spec,executable-spec,story - For bugs:
bug,defect,fix
All feature-related types will create an Executable Spec in JIRA. All bug-related types will create a Bug in JIRA.
Step 1: Analyze Codebase Context
Based on the issue type and description, I'll analyze the codebase to gather relevant context:
For Executable Specs:
-
Search for Related Implementations
- Check if similar features exist
- Identify integration points
- Find relevant patterns to follow
- Locate appropriate directories for new code
-
Analyze Architecture
- Understand current system design
- Identify affected components
- Check for conflicting implementations
- Review configuration structures
For Bugs:
-
Investigate Symptoms
- Search for error patterns in code
- Find related log statements
- Identify affected components
- Check recent changes that might have introduced the issue
-
Reproduce Understanding
- Analyze code flow where bug occurs
- Identify root cause possibilities
- Find related test cases
- Check for similar fixed issues
Step 2: Gather Additional Information
I'll ask you a few clarifying questions based on what I find:
For Executable Specs:
- What problem does this feature solve?
- Who are the primary users/consumers?
- Are there any performance or scalability requirements?
- Should this be configurable? If so, how?
- Any specific acceptance criteria you already have in mind?
For Bugs:
- When did this issue first appear?
- What are the exact steps to reproduce?
- What is the expected behavior vs actual behavior?
- How critical is this issue (blocking production, affecting users, etc.)?
- Any error messages or stack traces?
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 · 197 lines · 0 tokens per session scan A 71b1a7266876
create-jira-issue is a command published in the GitHub repository SAGAAIDEV/mcp-ahrefs (0 stars, last pushed 1y ago), licensed MIT. It adds 26 tokens to every session and 1,428 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-31.
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.