Borrowing it
Nothing to install: this file belongs to parawanderer/OpenTagViewer. 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/parawanderer/OpenTagViewer/main/.claude/skills/investigating-bug-reports/SKILL.mdgit clone --depth 1 https://github.com/parawanderer/OpenTagViewerWrote 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/parawanderer/opentagviewer/investigating-bug-reports)<a href="https://agentmods.dev/skills/parawanderer/opentagviewer/investigating-bug-reports"><img src="https://agentmods.dev/badge/skills/parawanderer/opentagviewer/investigating-bug-reports/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/parawanderer/opentagviewer/investigating-bug-reports"><img src="https://agentmods.dev/badge/skills/parawanderer/opentagviewer/investigating-bug-reports.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.00050 | $0.01763 |
| Opus 5.5 | $0.00020 | $0.00705 |
| Sonnet 5.5 | $0.00010 | $0.00353 |
| Haiku 4.5 | $0.00005 | $0.00176 |
Grade A, and why
investigating-bug-reports scanned grade A with 1 finding 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 16d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL -o "$SCRATCH/shot1.png" "https://github.com/user-attachments/assets/<id>" How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reading a bug report before answering it
The failure this exists for is concluding "there is not enough here" while the answer is in the thread. It is not a slower diagnosis; it is asking somebody to send a thing they already sent, then reasoning from a guess while waiting for it.
Two things get missed, and both are invisible in the obvious gh call.
1. Pull the whole thread, not the body
gh issue view <n> prints the body. The diagnosis is often three comments down — a reporter who
answered a question, a second person with the same symptom on different hardware, or the reporter
correcting their own title.
gh issue view <n> --json number,title,author,createdAt,state,labels,body,comments \
--jq '"#\(.number) \(.title)\nby \(.author.login) at \(.createdAt) [\(.state)]\n\n\(.body)\n\n--- COMMENTS ---\n"
+ ([.comments[] | "[\(.author.login) \(.createdAt)]\n\(.body)"] | join("\n\n"))'
gh issue view <n> --comments has come back empty here on an issue that has comments, which is
why the --json form is the one written down. A blank result from the convenience flag is not
evidence the thread is empty — check with the JSON before believing it.
2. Read the images. This is the one that gets skipped
This is a phone app, so its errors arrive on a screen, so that is how they get reported. The template's log field and "what happened" field are routinely empty while a screenshot carries the whole thing — pasting a screenshot is one gesture, capturing a log is a menu, a file and a decision about what to redact.
gh gives you the URL, not the picture, and an <img> tag sitting in a body reads like decoration
next to prose. A report whose fields are blank is not a report with nothing in it. It is one
where everything is in the attachment.
Then download each one and Read it. The Read tool renders an image, but only from a local
path — there is no fetching an image straight from a URL:
curl -sL -o "$SCRATCH/shot1.png" "https://github.com/user-attachments/assets/<id>"
file "$SCRATCH/shot1.png" # confirm it is a PNG and not an HTML error page
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.
- 16d ago Changed · +5 lines a51839e0f9bc
- 1mo ago First seen · 127 lines · 50 tokens per session scan A 71a67d32393e
investigating-bug-reports is a skill published in the GitHub repository parawanderer/OpenTagViewer (450 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 1,763 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-17.
Other skills, from other repositories
argent-metro-debugger
Debug a JS runtime via CDP using argent debugger tools. Primary path is React Native via Metro (iOS / Android / Vega); a subset of the tools (debugger-connect, debugger-status, debugger-evaluate, debugger-log-registry) also drive a Chromium (CDP) app's renderer (an Electron app, or any Chromium browser exposing CDP)…
argent-react-native-optimization
Optimizes a React Native app by profiling first to find real bottlenecks, then sweeping for mechanical issues. Entry-point for all performance work. Use when the app feels slow, user asks to optimize, fix re-renders, reduce jank, or improve startup. Delegates to argent-react-native-profiler for measurement.
nightly-audit-engineer-getting-started
A first-conversation guide for setting up a code-audit assistant. A code audit is a focused review of source code for defects or risky behavior, with the needed repository, scope, concerns, permissions, and schedule clarified first.
nightly-audit-engineer-ops
A workflow for reviewing code for reproducible quality problems and recording the evidence behind each finding. It follows data through inputs, permissions, storage, asynchronous work, and recovery, then suggests the smallest authorized fix.
nightly-audit-engineer-evidence
A small local checker that creates stable identifiers for code-audit findings and marks duplicates within the current batch or among previously seen findings. It processes supplied JSON with Python and does not infer whether a problem was fixed.
argent-native-profiler
Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.