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/complete-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/complete-issue)<a href="https://agentmods.dev/commands/sagaaidev/mcp-ahrefs/complete-issue"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/complete-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/complete-issue"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/complete-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.00023 | $0.00750 |
| Opus 5.5 | $0.00009 | $0.00300 |
| Sonnet 5.5 | $0.00005 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
complete-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 2mo 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I'll help you complete the current issue by committing changes, creating a pull request, and updating the JIRA issue.
Parse Arguments
- Site alias provided: $ARGUMENTS (e.g., "saaga")
- I'll extract the JIRA issue key from the current branch name
Step 1: Review Changes
First, let me check the current status:
!git status !git diff --stat
Step 2: Run Quality Checks
Running linting and tests before committing:
!ruff check . !pytest
Step 3: Stage and Commit Changes
I'll stage all changes and create a detailed commit message:
!git add -A
The commit message will follow conventional commits format based on issue type:
- Feature/Story:
feat: [Description] - Bug:
fix: [Description] - Task:
task: [Description] - Other:
chore: [Description]
The commit will include:
- Brief description
- Detailed changes
- Reference to JIRA issue
- Claude Code attribution
Step 4: Push Branch
!git push -u origin $(git branch --show-current)
Step 5: Create Pull Request
Using GitHub CLI to create the PR with appropriate title based on issue type:
gh pr create \
--title "[TYPE]: [Description based on commits]" \
--body "## Summary
- Key changes implemented
## Related Issue
Closes [ISSUE-KEY from branch name]
## Test Plan
- ✅ Unit tests pass
- ✅ Integration tests pass
- ✅ Linting passes
- ✅ Regression tests pass (for bug fixes)
🤖 Generated with [Claude Code](https://claude.ai/code)" \
--assignee @me
PR title prefix will be:
- Feature/Story:
feat: - Bug:
fix: - Task:
task: - Other:
chore:
Step 6: Update JIRA to Done
After the PR is created, I'll:
- Extract the JIRA issue key from the branch name (e.g., feature/ACT-123-description → ACT-123)
- Add the PR link as a comment on the JIRA issue using mcp__mcp_jira__update_jira_issue with the provided site alias
- Update the issue status to 'Done' using mcp__Conduit__update_jira_status with the site alias
Let's start by reviewing your changes...
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.
- 2mo ago First seen · 106 lines · 23 tokens per session scan A 47413dd21195
complete-issue is a command published in the GitHub repository SAGAAIDEV/mcp-ahrefs (0 stars, last pushed 1y ago), licensed MIT. It adds 23 tokens to every session and 750 once invoked, about $0.0001 per session on Opus 5.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
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
standup
Review my git commits from the past workday and generate a standup summary.
gsd:remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
iterate
Execute a single Ralph loop iteration - complete one work unit from tasks.md with proper commits and progress tracking.
weekly-summary
Generate weekly work summary from git activity.
end-work
Complete work session with final checklist.