Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add shopwareLabs/ai-coding-tools --skill issue-analyzinggit clone --depth 1 https://github.com/shopwareLabs/ai-coding-toolsWrote 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/shopwarelabs/ai-coding-tools/issue-analyzing)<a href="https://agentmods.dev/skills/shopwarelabs/ai-coding-tools/issue-analyzing"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/issue-analyzing/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/shopwarelabs/ai-coding-tools/issue-analyzing"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/issue-analyzing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.01390 |
| Opus 5.5 | $0.00020 | $0.00556 |
| Sonnet 5.5 | $0.00010 | $0.00278 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
issue-analyzing 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Analyzing
Analyze a GitHub issue by combining authoritative issue data from GitHub with semantic code research from ChunkHound. Produces a structured analysis of problem scope, affected code area, and resolution status.
Do not activate for generic code questions that do not reference a specific issue.
Prerequisites
Requires the chunkhound-integration companion plugin. The skill calls mcp__plugin_chunkhound-integration_ChunkHound__code_research at Step 3 and stops with an error if that tool is not callable — see Errors.
Issue data is fetched from GitHub using whatever access the session has available (a GitHub MCP server, the gh CLI, or direct API calls).
Input
- Required: Issue number
- Optional: Repository as
owner/name— defaults to the current repository context - Optional: Triage reasoning — context from the caller about why analysis was requested. Treat as a hint for research focus.
Workflow
Step 1 — Fetch issue data
Fetch the following from GitHub: issue metadata (title, body, author, labels, state) and all comments.
Use whatever GitHub access is available in the session. If a single call returns everything together, that's fine; if comments are returned separately, fetch them as part of this step. On error (issue not found, access denied, no GitHub access), stop and report to the user.
Step 2 — Identify the affected code area
From the issue description and comments, extract signals about what part of the codebase is affected:
- File paths or component names mentioned directly in the description
- Class or function names referenced in the text (often in backticks or stack traces)
- Error messages that can be traced back to specific components
- Area labels (e.g.,
area/checkout,area/admin) that indicate scope - Linked PRs referenced as fixes — comments often contain "Fixed in #X" or "See PR #Y"
If the issue is a feature request, the "affected area" is the area that would need to change to implement it. If the body is too vague to identify a specific area, note this in the output and research at the area label's level instead.
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 First seen · 100 lines · 51 tokens per session scan A be743837073f
issue-analyzing is a skill published in the GitHub repository shopwareLabs/ai-coding-tools (45 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 1,390 once invoked, about $0.0002 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-30.
Other skills, from other repositories
review-pr
Comprehensive PR review -- full branch diff against base, commit-by-commit analysis, breaking change detection, conventional commit verification.
oss-contrib
Use when contributing to open source projects from forked repositories. Handles upstream sync, CONTRIBUTING.md compliance, code style matching, PR preparation, and project-specific patterns. Activates for fork management, PR template filling, and upstream workflow compliance.
release
This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and publish to npm through the release workflow. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".
dev-workflow
Use when performing common development tasks like committing code, reviewing changes, running tests, fixing bugs, creating PRs, or checking repo status. Provides structured workflows for everyday git and development operations.
babysit
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.