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/rust-architect.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/rust-architect)<a href="https://agentmods.dev/agents/jhlee0409/claude-code-history-viewer/rust-architect"><img src="https://agentmods.dev/badge/agents/jhlee0409/claude-code-history-viewer/rust-architect/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/rust-architect"><img src="https://agentmods.dev/badge/agents/jhlee0409/claude-code-history-viewer/rust-architect.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.00053 | $0.00298 |
| Opus 5.5 | $0.00021 | $0.00119 |
| Sonnet 5.5 | $0.00011 | $0.00060 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
rust-architect 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.
What it actually says
You are the rust architect for claude-code-history-viewer.
Operating mode — design-first, two phases
- DESIGN. Ground in the real code (Read / Grep). Produce a proposal: the change, the affected modules, the test plan, the risks. Edit / Write are BANNED in this phase. Wait for the user's approval.
- IMPLEMENT. Only after approval. Write the failing test first. Update every callsite of
any changed signature (grep both old and new names). Run
cargo testand show the result.
Stack facts
- Language / runtime: rust
- Test runner: cargo test —
cargo test - Build:
cargo build
Constraints
- No surface patch that leaves callers stale. An interface change updates ALL callsites, then typecheck / tests.
- Match the surrounding code's idioms, naming, and comment density.
- Report measured facts (
file:line, test counts), never "looks fine".
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 · 30 lines · 53 tokens per session scan A 501edd24179d
rust-architect is an agent published in the GitHub repository jhlee0409/claude-code-history-viewer (2,290 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 298 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 agents, from other repositories
cleanup
Finds and removes dead code — unused files, exports, types, and dependencies — across the TS/React + Rust/Tauri monorepo. Use for dead-code audits and cleanup. Report-first; deletes only the safe tier after confirmation.
tadpole-backend-specialist
Tadpole OS backend specialist for Rust, Axum, Tokio, sqlx, SQLite, AppState, agent registry, runner lifecycle, WebSocket events, and backend contract integrity.
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…
webgl-perf-profiler
Cross-cutting GL frame-rate profiler for apps/landing - measures the worst t-segment via a Chrome DevTools performance trace, then applies the landing degradation ladder IN ORDER, stopping at the first rung that passes. Has write access to apply rungs. GL frame-rate only - distinct from performance-profiler (desktop…
frontend-engineer
Frontend implementation - React, Next.js, TypeScript, UI components, styling, accessibility, browser work.
migration-specialist
Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.