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 agentmods add instructions/d-kimuson/claude-code-viewer/agents-mdgit clone --depth 1 https://github.com/d-kimuson/claude-code-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/instructions/d-kimuson/claude-code-viewer/agents-md)<a href="https://agentmods.dev/instructions/d-kimuson/claude-code-viewer/agents-md"><img src="https://agentmods.dev/badge/instructions/d-kimuson/claude-code-viewer/agents-md.svg" alt="Measured on agentmods" 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 | $0.01507 | $0.01507 |
| Opus 5 | $0.00754 | $0.00754 |
| Sonnet 5 | $0.00301 | $0.00301 |
| Haiku 4.5 | $0.00151 | $0.00151 |
Grade A, and why
claude-code-viewer AGENTS.md 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 4d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Use `Command.string` instead of `child_process` Copies of this mod
1 near-identical copy found in the catalogue:
- claude-code-viewer CLAUDE.md — 89% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Critical Rules (Read First)
Language:
- Code, comments, and commit messages should be in English
NEVER:
- Use
astype casting in ANY context including test code (explain the problem to the user instead) - Use raw
fetchor bypass TanStack Query for API calls - Run
pnpm devorpnpm start(dev servers) - Use
node:fs,node:path, etc. directly (use Effect-TS equivalents)
ALWAYS:
- Use Effect-TS for all backend side effects
- Use Hono RPC + TanStack Query for all API calls
- Follow TDD: write tests first, then implement
- Run
pnpm typecheckandpnpm fixbefore committing
Commit Message Rules
Conventional Commits format: type: description
Release Note Awareness:
- Commit messages are included in release notes; write for users.
Type Selection:
| Type | Release Note | Purpose |
|---|---|---|
feat |
Features | User-facing new feature |
fix |
Bug Fixes | User-impacting bug fix |
chore, ci, build, refactor |
Excluded | Internal changes |
Critical: Use fix only for user-facing bugs. Internal fixes (linter errors, type errors, build scripts) must use chore.
Message Quality Examples:
- Bad:
fix: fix lingui error(internal issue) - Bad:
feat: add button(too vague) - Good:
feat: add dark mode toggle to settings - Good:
fix: session list not updating after deletion - Good:
chore: update lingui compiled messages
Project Overview
Claude Code Viewer reads Claude Code session logs directly from JSONL files (~/.claude/projects/) with zero data loss. It's a web-based client built as a CLI tool serving a Vite application.
Core Architecture:
- Frontend: Vite + TanStack Router + React 19 + TanStack Query
- Backend: Hono (standalone server) + Effect-TS (all business logic)
- Data: Direct JSONL reads with strict Zod validation
- Real-time: Server-Sent Events (SSE) for live updates
Recommended Coding Process
This project is designed with the philosophy of achieving both rapid feedback and code quality maintenance (passing checks = nearly guaranteed runtime correctness) by leveraging:
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.
- 4d ago First seen · 187 lines · 1,507 tokens per session scan A 32b5bbe52ce1
claude-code-viewer AGENTS.md is an instructions file published in the GitHub repository d-kimuson/claude-code-viewer (1,278 stars, last pushed 16d ago), licensed MIT. It adds 1,507 tokens to every session, about $0.0075 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.