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/start-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/start-issue)<a href="https://agentmods.dev/commands/sagaaidev/mcp-ahrefs/start-issue"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/start-issue.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.00028 | $0.01284 |
| Opus 5 | $0.00014 | $0.00642 |
| Sonnet 5 | $0.00006 | $0.00257 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
start-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 6d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I'll help you start working on JIRA issue $ARGUMENTS. Let me parse the issue key and site alias, then fetch the issue details and set up your development environment.
Parse Arguments
Let me extract the issue key and site alias from the provided arguments:
- Arguments provided: $ARGUMENTS
- Expected format: [ISSUE-KEY] [SITE-ALIAS] (e.g., "ACT-123 saaga")
Step 1: Fetch JIRA Issue
I'll use the parsed issue key and site alias to fetch the JIRA issue:
- Use mcp__mcp_jira__search_jira_issues to search for the issue
- The JQL query will be: key = [ISSUE-KEY]
- Using the provided site_alias
Step 2: Analyze Existing Codebase
Before creating a branch, I'll analyze the current codebase to determine if this feature:
- Already exists (fully implemented)
- Partially exists (some components in place)
- Conflicts with existing architecture
- Is no longer relevant (deprecated approach or outdated requirement)
Analysis Strategy:
- Extract Key Requirements from JIRA issue description and acceptance criteria
- Search for Existing Implementations:
- Use Grep/Task to search for keywords from the issue
- Look for function names, class names, or patterns mentioned
- Check for similar UI components or endpoints
- Review recent commits for related work
- Analyze Project Structure:
- Check if mentioned files/directories already exist
- Look for competing implementations
- Review configuration for feature flags or existing settings
- Check Documentation:
- Search README and docs for feature mentions
- Look for deprecated notices or architecture decisions
Decision Points:
-
If Fully Implemented:
- ❌ Stop and report findings
- Suggest closing JIRA issue or converting to documentation task
- Show evidence of existing implementation
-
If Partially Implemented:
- 🔄 Document what exists vs. what's missing
- Adjust implementation plan to build on existing work
- Note potential refactoring needs
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.
- 6d ago First seen · 138 lines · 28 tokens per session scan A d65b8db9bddf
start-issue is a command published in the GitHub repository SAGAAIDEV/mcp-ahrefs (0 stars, last pushed 1y ago), licensed MIT. It adds 28 tokens to every session and 1,284 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
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
next
Suggest the most likely next workflow action based on current context.
weekly-summary
Generate weekly work summary from git activity.