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/fremat79/claudecodeexplorer/claude-mdgit clone --depth 1 https://github.com/fremat79/ClaudeCodeExplorerWrote 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/fremat79/claudecodeexplorer/claude-md)<a href="https://agentmods.dev/instructions/fremat79/claudecodeexplorer/claude-md"><img src="https://agentmods.dev/badge/instructions/fremat79/claudecodeexplorer/claude-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.01169 | $0.01169 |
| Opus 5 | $0.00584 | $0.00584 |
| Sonnet 5 | $0.00234 | $0.00234 |
| Haiku 4.5 | $0.00117 | $0.00117 |
Grade A, and why
ClaudeCodeExplorer CLAUDE.md 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 3d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this app is
A WPF (.NET 10, Windows) tray application that scans ~/.claude/projects, parses each
Claude Code session transcript (.jsonl), and presents the conversations as searchable,
project-grouped tiles. Clicking a tile opens Windows Terminal in that conversation's
original working directory and runs claude --resume <sessionId>.
Commands
dotnet build # Debug build
dotnet build -c Release # Release (DebugType=none)
dotnet run # build + launch (starts hidden in the tray)
dotnet publish -p:PublishProfile=FolderProfile # single-file, self-contained, win-x64, R2R
There is no test project and no linter configured — build is the only gate.
Architecture
MVVM, but hand-rolled (no MVVM framework). The single window binds to MainViewModel;
all real work lives in stateless static service classes under Services/.
Data flow (read path):
ProjectScanner.Scan enumerates ~/.claude/projects/<encoded-path>/*.jsonl →
for each file, CacheService.TryGet returns a cached ConversationInfo if the file's
last-write-time-ticks and size are unchanged, otherwise JsonlParser.Parse reads it →
results sorted by LastActivityUtc desc → surfaced through MainViewModel.ConversationsView
(an ICollectionView that filters by SearchBlob and groups by WorkingDirectory).
Scanning runs on a background thread (Task.Run) and parses files in parallel
(Parallel.ForEach). The parse result cache is persisted to
%LOCALAPPDATA%\ClaudeCodeExplorer\cache.json; ConversationInfo must stay
System.Text.Json-serializable because it is the cache record (note the [JsonIgnore]
SearchBlob).
Data flow (actions): MainViewModel commands delegate to TerminalLauncher
(resume / open terminal / open in Explorer) and to local Delete. Everything the user
triggers is wrapped in Run(...) which shows exceptions as a MessageBox.
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.
- 3d ago First seen · 87 lines · 1,169 tokens per session scan A 76030df7ce7b
ClaudeCodeExplorer CLAUDE.md is an instructions file published in the GitHub repository fremat79/ClaudeCodeExplorer (5 stars, last pushed 15d ago), licensed MIT. It adds 1,169 tokens to every session, about $0.0058 per session on Opus 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-31.
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.