Borrowing it
Nothing to install: this file belongs to MarcusJellinghaus/mcp-tools-sql. 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/MarcusJellinghaus/mcp-tools-sql/main/.claude/skills/issue_analyse/SKILL.mdgit clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-sqlWrote 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/skills/marcusjellinghaus/mcp-tools-sql/issue_analyse)<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-sql/issue_analyse"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/issue_analyse/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/skills/marcusjellinghaus/mcp-tools-sql/issue_analyse"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/issue_analyse.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.00011 | $0.00572 |
| Opus 5.5 | $0.00004 | $0.00229 |
| Sonnet 5.5 | $0.00002 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
issue_analyse 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 1mo 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.
This is a copy
88% identical to issue_analyse — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyse GitHub Issue
Fetch a GitHub issue and analyze its requirements, feasibility, and potential implementation approaches.
Resolve Issue Number
The user may provide an issue number as the argument (available as $ARGUMENTS).
If no issue number is provided:
- Read
.vscodeclaude_status.txtand extract the issue number from theIssue #NNNline - If the file doesn't exist or has no issue number, ask the user
Wait one second using mcp__mcp-tools-py__sleep with sleep_seconds: 1.
Fetch the issue:
Call mcp__mcp-workspace__github_issue_view with the issue number.
Instructions
Analyze the issue:
Can we discuss this requirement / implementation idea and its feasibility? Please also look at the code base to understand the context (using the different tools with access to the project directory). Do not provide code yet!
At the end of our discussion, I want to have an even better issue description.
Decision-awareness:
If the issue contains a ## Decisions section, read it carefully:
- Do NOT re-ask topics that are already decided. Focus on aspects not yet covered.
- If any existing decision seems risky or questionable given what you see in the code, briefly note the concern — but don't block on it.
Constraints identification:
During the discussion, actively identify constraints and rationale — the "why" behind decisions, non-obvious gotchas, things that downstream steps (/create_plan, /implement) need to know. These will be captured in the issue via /issue_update.
Base Branch Handling:
If the issue contains a ### Base Branch section:
- Display the specified base branch prominently
- Verify the branch exists using: call
mcp__mcp-workspace__gitwith command"ls_remote"and args["--heads", "origin", "<branch-name>"] - If the branch does NOT exist, show a clear warning: "⚠️ Warning: Base branch 'X' does not exist on remote. Branch creation will fail."
- Continue with the analysis (non-blocking error)
Focus on:
- Understanding the problem/feature request
- Technical feasibility
- Potential implementation approaches
- Questions that need clarification
- Impact on existing code
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.
- 1mo ago Changed · -3 lines fce3a2cafb32
- 1mo ago First seen · 63 lines · 11 tokens per session scan A 49fa822c279f
issue_analyse is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-sql (2 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 572 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to issue_analyse, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…