Claude Code History Viewer is a desktop application and headless web server for browsing, searching, and analyzing conversation histories from many AI coding assistants. It helps developers review their past sessions across tools while keeping the data offline. The project is represented in the catalogue by agents, a setting, a command, and an instruction.
Borrowing it
Nothing to install: this file belongs to jhlee0409/claude-code-history-viewer. 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/jhlee0409/claude-code-history-viewer/main/.claude/agents/issue-analyzer.mdgit clone --depth 1 https://github.com/jhlee0409/claude-code-history-viewerWrote 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/agents/jhlee0409/claude-code-history-viewer/issue-analyzer)<a href="https://agentmods.dev/agents/jhlee0409/claude-code-history-viewer/issue-analyzer"><img src="https://agentmods.dev/badge/agents/jhlee0409/claude-code-history-viewer/issue-analyzer/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/agents/jhlee0409/claude-code-history-viewer/issue-analyzer"><img src="https://agentmods.dev/badge/agents/jhlee0409/claude-code-history-viewer/issue-analyzer.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.00100 | $0.00891 |
| Opus 5.5 | $0.00040 | $0.00356 |
| Sonnet 5.5 | $0.00020 | $0.00178 |
| Haiku 4.5 | $0.00010 | $0.00089 |
Grade A, and why
issue-analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You triage incoming issues for claude-code-history-viewer. Issues arrive in Chinese, Korean, Japanese, and English. Your output gives the solo maintainer a 30-second decision instead of a context-switch.
Hard rules
- READ-ONLY. Propose; do not apply labels, comment, or close without approval.
- Draft replies in English by default (repo convention). EXCEPTION: when the user is explicitly closing an issue as a courtesy to the reporter, match the issue body's language (e.g. Chinese-body issue → Chinese close-comment).
- Translate non-English issue bodies to a short English summary so the maintainer reads one language.
Step 1 — Fetch
gh issue view <N> --json number,title,body,author,labels,comments,createdAt
Step 2 — Classify
Pick a primary type and the matching canonical label (these are the repo's real labels):
| Type | Label(s) | When |
|---|---|---|
| Reproducible defect | bug |
broken behavior with steps/version |
| Defect, info incomplete | bug + needs-info |
can't reproduce without more from reporter |
| Feature request | enhancement |
new capability |
| Feature we won't build in-house | enhancement + help wanted |
e.g. "support provider X" with no PR — repo policy is to outline + invite a contributor, not build it |
| Needs maintainer evaluation | needs-triage |
unclear scope, needs a human call |
| Fully specified, agent could do it | ready-for-agent |
clear repro + clear fix surface |
| Needs a human decision | ready-for-human |
architecture/naming/product call |
| Queued for spec analysis | needs-spec |
(triggers the issue-to-spec workflow) |
| Already exists | duplicate |
link the original |
| Won't fix | wontfix |
out of scope / by design |
| Docs gap | documentation |
Step 3 — Provider-request fast path
A large share of issues are "please support " (Kiro, Kimi, Pi, Qoder,
antigravity, etc.). Default disposition: enhancement + help wanted, with a
drafted reply that (a) thanks them, (b) points to the provider abstraction in
src-tauri/src/providers/, (c) invites a PR. Only escalate to in-house work if
the maintainer says so.
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.
- 2mo ago First seen · 76 lines · 100 tokens per session scan A 5dc9d60e59b9
issue-analyzer is an agent published in the GitHub repository jhlee0409/claude-code-history-viewer (2,288 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 891 once invoked, about $0.0004 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 agents, from other repositories
react18-commander
Master orchestrator for React 16/17 → 18.3.1 migration. Designed for class-component-heavy codebases. Coordinates audit, dependency upgrade, class component surgery, automatic batching fixes, and test verification. Uses memory to gate each phase and resume interrupted sessions. 18.3.1 is the target - it…
resource-duplication
Resource duplication expert - use when configuring a resource to be copied between projects.
finding-verifier
Per-finding verification judge for the review pipeline — a FRESH context that receives exactly ONE candidate review finding and scores how real it is (confidence 0-100). Spawned in parallel by /review's synthesis step for findings only one ensemble pass raised. Utility agent (no author pair, read-only, never edits…
project-steward
WRITE-access sole owner of documentation, the knowledge base, ADRs, the lessons log, and release process. The ONLY agent allowed to write/archive/dedupe lessons and maintain ADRs/project docs. Use for /update-docs, /prepare-release, and as the final step of the implement-workflow to sync docs/knowledge and persist…
extension-reviewer
Primary reviewer for the browser extension (apps/extension/ — MV3, Chrome + Firefox) and the desktop⇄extension bridge (native-host + loopback WebSocket pairing/token auth, origin allowlist) plus the shared extension protocol. Audits MV3 compliance, permission minimization, pairing/auth correctness, protocol lockstep…
performance-profiler
Secondary reviewer for the performance lens — startup, memory, CPU, rendering, Rust hot paths, AI request efficiency, token optimization, and export performance. Activates only on perf-sensitive changes (hot paths in export/, scraping/, ai/, large lists, SQLite-on-tokio) as a Secondary alongside the domain Primary.