An automated issue-testing command that examines the project and chooses between MCP, API, and UI testing, as well as direct or subprocess execution. UI testing checks the visible application, while API testing checks its programmatic interfaces.

Use it to test an issue by inspecting the current branch, recent changes, test files, dependencies, and clues such as frontend files or UI-related wording.

It removes the need to manually decide which testing method fits an issue and the project’s existing tools.

How SAGAAIDEV/mcp-ahrefs configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/SAGAAIDEV/mcp-ahrefs/main/.claude/commands/test-issue.md

Clone the repo

git clone --depth 1 https://github.com/SAGAAIDEV/mcp-ahrefs

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/test-issue/github.svg)](https://agentmods.dev/commands/sagaaidev/mcp-ahrefs/test-issue)

Your own site

<a href="https://agentmods.dev/commands/sagaaidev/mcp-ahrefs/test-issue"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/test-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sagaaidev/mcp-ahrefs/test-issue"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/test-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,112 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00027	$0.01112
Opus 5.5	$0.00011	$0.00445
Sonnet 5.5	$0.00005	$0.00222
Haiku 4.5	$0.00003	$0.00111

Measured 2mo ago against content hash a258e7a4078b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

test-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.

.claude/commands/test-issue.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

I'll analyze the current issue and automatically determine the best testing approach.

Step 1: Analyze Context

First, let me gather information to determine the testing approach:

Check Current Branch

!git branch --show-current

Analyze Recent Changes

!git diff --name-only HEAD~1..HEAD

Look for Test Patterns

!find . -name ".test." -o -name ".spec." -o -name "_test." | head -20

Check Package Dependencies

!test -f package.json && grep -E "(puppeteer|playwright|selenium|jest|mocha|cypress)" package.json || echo "No package.json found" !test -f requirements.txt && grep -E "(selenium|playwright|pytest)" requirements.txt || echo "No requirements.txt found"

Step 2: Detection Logic

Based on the analysis, I'll determine the testing approach:

Indicators for UI Testing (Puppeteer):

Changes to files in: src/components/, src/pages/, src/views/, app/, frontend/
File extensions: .jsx, .tsx, .vue, .svelte
Presence of: package.json with React/Vue/Angular/Svelte
JIRA issue mentions: UI, interface, button, form, page, screen, responsive
Existing tests using: Puppeteer, Playwright, Cypress, Selenium

Indicators for Backend API Testing (PyTest):

Changes to files in: api/, backend/, routers/, endpoints/, controllers/
File extensions: .py with FastAPI/Flask/Django decorators (@app.route, @router, @api_view)
Presence of: FastAPI, Flask, Django REST in requirements.txt
JIRA issue mentions: API, endpoint, REST, HTTP, request, response, validation
Existing tests using: pytest, TestClient, httpx
Files containing: test_*.py or *_test.py in tests/ directory

Indicators for MCP Testing:

Changes to files in: mcp/, tools/
File extensions: .py with @mcp_server decorators
Presence of: MCP server configuration
JIRA issue mentions: MCP tool, integration with external services
Current project is identified as MCP server

Indicators for Hybrid Testing:

Full-stack changes (both frontend and backend)
JIRA issue mentions end-to-end functionality
Changes span multiple layers

Read the full file on GitHub · 130 lines

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 · 130 lines · 27 tokens per session scan A a258e7a4078b

Subscribe to this mod's changes

test-issue is a command published in the GitHub repository SAGAAIDEV/mcp-ahrefs (0 stars, last pushed 1y ago), licensed MIT. It adds 27 tokens to every session and 1,112 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.

Testing

prototype

You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.

grainulation/grainulator · 0 tokens

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

mcp-ahrefs: Command for Claude Code