mcpadvisor: Command for Claude Code

.claude/commands/issue.md

issue is a command for Claude Code from istarwyh/mcpadvisor. It costs 0 tokens per session (1,786 once invoked), scanned A, original, MIT.

A command for investigating and fixing a GitHub issue, a tracked report of a bug, request, or other task.

In plain words
What is it for?
Use it with an issue number or description to inspect the report, search the codebase and related pull requests, and prepare a fix.
Why use it?
It provides a repeatable path from understanding the issue and related project history to planning, coding, testing, and documentation.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md; names the TodoWrite tool; mentions Claude Code.

This is istarwyh/mcpadvisor's own configuration. It tells Claude Code how to work on mcpadvisor itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcpadvisor configures →

Reuse

Borrowing it

Nothing to install: this file belongs to istarwyh/mcpadvisor. 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/istarwyh/mcpadvisor/main/.claude/commands/issue.md
Clone the repo
git clone --depth 1 https://github.com/istarwyh/mcpadvisor

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.

agentmods badge for issue

README.md
[![agentmods](https://agentmods.dev/badge/commands/istarwyh/mcpadvisor/issue/github.svg)](https://agentmods.dev/commands/istarwyh/mcpadvisor/issue)
Your own site
<a href="https://agentmods.dev/commands/istarwyh/mcpadvisor/issue"><img src="https://agentmods.dev/badge/commands/istarwyh/mcpadvisor/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.

agentmods 80×15 button for issue

Your own site · 80×15
<a href="https://agentmods.dev/commands/istarwyh/mcpadvisor/issue"><img src="https://agentmods.dev/badge/commands/istarwyh/mcpadvisor/issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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,786 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01786
Opus 5.5 $0.00000 $0.00714
Sonnet 5.5 $0.00000 $0.00357
Haiku 4.5 $0.00000 $0.00179

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

Security

Grade A, and why

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/issue.md · 248 lines

How it starts

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

Please analyze and fix the Github issue: $ARGUMENTS.

Follow these steps for comprehensive issue resolution:

PLAN

  1. Get issue details:

    gh issue view $ISSUE_NUMBER
    
  2. Understand the problem described in the issue:

    • Read the issue description carefully
    • Check any attached screenshots or logs
    • Understand the expected vs actual behavior
    • Identify the scope (bug fix vs feature implementation)
  3. Ask clarifying questions if necessary in issue comments

  4. Research prior art and context:

    • Search existing documentation in docs/ for related information
    • Search PRs to see if you can find history on this issue:
      gh pr list --search "keyword from issue"
      
    • Search the codebase for relevant files using Grep/Glob tools
    • Check if similar issues have been resolved before
  5. Break down the work using TodoWrite tool:

    • Identify all components that need changes
    • Plan implementation steps
    • Consider testing requirements
    • Plan documentation updates
  6. Create documentation plan:

    • Determine which docs/ files need updates
    • Plan new documentation if implementing features
    • Consider updating:
      • docs/GETTING_STARTED.md for user-facing features
      • CONTRIBUTING.md for development changes
      • docs/ARCHITECTURE.md for architectural changes
      • docs/TECHNICAL_REFERENCE.md for technical implementations
      • Create issue-specific docs in docs/ with appropriate categorization

PRE-TEST VALIDATION

  • Switch to main branch and create new branch for the issue:

    # Ensure you're starting from the latest main branch
    git checkout main
    git pull origin main
    
    # Create and switch to new feature branch
    git checkout -b issue-$ISSUE_NUMBER-brief-description
    

    Important: Always start from main to ensure your changes are based on the latest codebase and avoid merge conflicts.

  • Run the full test suite to ensure clean environment:

    pnpm run check          # Lint and format check
    pnpm run test           # Unit tests
    pnpm run test:coverage  # Coverage report
    pnpm run test:e2e       # End-to-end tests (if applicable)
    

Read the full file on GitHub · 248 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.

  1. 2mo ago First seen · 248 lines · 0 tokens per session scan A 9c1da3fa7783

Subscribe to this mod's changes

issue is a command published in the GitHub repository istarwyh/mcpadvisor (89 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,786 tokens. 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-30.