Borrowing it
Nothing to install: this file belongs to qauth-labs/qauth. 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/qauth-labs/qauth/main/.claude/skills/investigate-issue/SKILL.mdgit clone --depth 1 https://github.com/qauth-labs/qauthWrote 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/qauth-labs/qauth/investigate-issue)<a href="https://agentmods.dev/skills/qauth-labs/qauth/investigate-issue"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/investigate-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.
<a href="https://agentmods.dev/skills/qauth-labs/qauth/investigate-issue"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/investigate-issue.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.00021 | $0.00561 |
| Opus 5.5 | $0.00008 | $0.00224 |
| Sonnet 5.5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
investigate-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 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigate GitHub Issue
Investigate a GitHub issue to understand requirements and context. See
github-conventions for repo and gh CLI basics.
Your Task
When given an issue number or URL, gather all relevant information.
Investigation Steps
1. View Issue Details
gh issue view {number} --json title,body,labels,milestone,state,comments,assignees
2. View Issue Comments
gh issue view {number} --comments
3. Check Related Issues
# Search for related issues
gh issue list --search "{keywords} in:title,body" --state all --limit 10
4. Check Linked PRs
# View PRs that reference this issue
gh pr list --search "#{number}" --state all
5. View Closed Related Issues
gh issue list --state closed --search "{keywords}" --limit 5 --json number,title,body
Output Format
Provide a summary including:
- Issue Overview: Title, state, labels, milestone
- Summary: What the issue is about
- Tasks: Outstanding tasks from the checkbox list
- Technical Context: Key technical details
- Acceptance Criteria: What defines "done"
- Related Issues/PRs: Any linked work
- Blockers: Any dependencies or blockers identified
Sub-Issues Investigation
If the issue has sub-issues:
# Get issue ID for GraphQL
gh issue view {number} --json id --jq ".id"
# Query sub-issues (if any)
gh api graphql \
-H "GraphQL-Features: sub_issues" \
-f query='
query($id: ID!) {
node(id: $id) {
... on Issue {
subIssues(first: 20) {
nodes {
number
title
state
}
}
}
}
}
' \
-f id="{issue_id}"
Instructions
- Fetch the full issue details
- Parse the body to identify tasks, technical details, and acceptance criteria
- Check for related issues and PRs
- Summarize findings for the user
- Identify any blockers or dependencies
- Suggest next steps if appropriate
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 · 99 lines · 21 tokens per session scan A 3ccaae872c53
investigate-issue is a skill published in the GitHub repository qauth-labs/qauth (26 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 561 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-30.
Other skills, from other repositories
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
enable-check-includes-strict
Enable and migrate Chromium targets and directories to checkincludesstrict = true, diagnosing and resolving header include violations as part of the checkincludesstrict LSC. Use when adding directories to the allowlist, enabling strict header checks on targets, or resolving CHECKINCLUDESSTRICTUNTRIAGED targets.
resolve-handoff
Emit the complete Resolve handoff with exact modes, outcomes, test evidence, and publication state.
reproduce-and-fix-issues
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.