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/new-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/new-issue)<a href="https://agentmods.dev/commands/sagaaidev/mcp-ahrefs/new-issue"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/new-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/new-issue"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/new-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.00015 | $0.01118 |
| Opus 5 | $0.00008 | $0.00559 |
| Sonnet 5 | $0.00003 | $0.00224 |
| Haiku 4.5 | $0.00002 | $0.00112 |
Grade A, and why
new-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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I'll help you create a new Jira issue in project $ARGUMENTS.
Parse Arguments
Let me extract the project key and site alias from the provided arguments:
- Arguments provided: $ARGUMENTS
- Expected format: [PROJECT-KEY] default (e.g., "CLD saaga")
Step 1: Gather Information from User
Before creating the issue, I need to gather some comprehensive information from you to ensure the issue is descriptive, actionable, and properly categorized.
Ask the user for:
- Summary: A clear, concise title (ask for clarification if too vague)
- Description: Detailed explanation of what needs to be done
- Context: Why is this needed? What problem does it solve?
- Location: Where in the codebase will this work happen?
- Acceptance Criteria: How will we know when it's complete?
Step 2: Structure the Issue Description
Once I have the necessary information, I will use this template to structure the description:
## Goal
[Clear statement of what needs to be achieved]
## Context
[Background information and why this is needed]
## Project Location
Directory: `[Full path to the relevant directory]`
Repository: [If applicable]
## Tasks
- [ ] [Specific task 1]
- [ ] [Specific task 2]
- [ ] [Specific task 3]
- [ ] Update documentation
- [ ] Add tests if applicable
## Acceptance Criteria
- [Specific measurable outcome 1]
- [Specific measurable outcome 2]
- [Configuration/documentation is updated]
## Additional Notes
[Any other relevant information]
Step 3: Create the Issue
I will use the gathered information and the structured description to create the issue using Conduit or jira mcp server:
# Use Conduit to create the issue
mcp__<conduit|jira>__create_jira_issue(
project="{{cookiecutter.jira_project_key}}",
summary="[Descriptive summary from user]",
description="[Formatted description using template above]",
issue_type="[issue-type from arguments]"
)
Example Conversation Flow
Assistant: I'll help you create a Jira issue. Let me gather some information:
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 · 155 lines · 15 tokens per session scan A dd036b4111ce
new-issue is a command published in the GitHub repository SAGAAIDEV/mcp-ahrefs (0 stars, last pushed 1y ago), licensed MIT. It adds 15 tokens to every session and 1,118 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.