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/apappascs/claude-code-sessions/claude-mdgit clone --depth 1 https://github.com/apappascs/claude-code-sessionsWrote 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/apappascs/claude-code-sessions/claude-md)<a href="https://agentmods.dev/instructions/apappascs/claude-code-sessions/claude-md"><img src="https://agentmods.dev/badge/instructions/apappascs/claude-code-sessions/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.01342 | $0.01342 |
| Opus 5 | $0.00671 | $0.00671 |
| Sonnet 5 | $0.00268 | $0.00268 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
claude-code-sessions 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 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.
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.
Project Overview
Session intelligence plugin for Claude Code — reads ~/.claude/projects/ and ~/.claude/tasks/ to provide search, analytics, timeline, and task management across all Claude Code sessions. Built with Bun (TypeScript), Alpine.js SPA frontend, zero external runtime dependencies.
Commands
bun install # Install dependencies
bun test # Run all tests
bun test --watch # Watch mode
bun test tests/server.test.ts # Run a single test file
bun test --grep "pattern" # Run tests matching pattern
bun run typecheck # Typecheck (bunx tsc --noEmit)
bun run lint # Lint & format check (Biome)
bun run lint:fix # Auto-fix lint/format issues
bun run ui # Start UI server on :3000
bun run ui:open # Start + open browser
CLI usage (each lib file is directly runnable):
bun run lib/session-store.ts list [--project FILTER] [--sort recency|size|duration] [--limit N]
bun run lib/session-store.ts search "<query>" [--project FILTER] [--since DATE]
bun run lib/session-store.ts tasks [--status pending|completed|in_progress|all]
bun run lib/session-parser.ts stats <session.jsonl>
bun run lib/session-parser.ts export <session.jsonl> [--format md|txt]
Architecture
Four-layer stack:
lib/formatters.ts— Shared utilities (JSON serialization, truncation, timestamp parsing). No I/O.lib/session-parser.ts— Single-session JSONL parser. Extracts stats, tasks, messages, tools, diffs from one.jsonlfile. Also a CLI.lib/session-store.ts— Cross-session operations. Scans~/.claude/projects/directory tree to list, search, filter, and aggregate across all sessions. Also a CLI.ui/server.ts— Bun HTTP server. Imports from lib, exposes REST endpoints (/api/sessions,/api/search,/api/tasks,/api/dashboard/stats, etc.), serves static files fromui/public/.
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 · 87 lines · 1,342 tokens per session scan A c4f77aec3da2
claude-code-sessions CLAUDE.md is an instructions file published in the GitHub repository apappascs/claude-code-sessions (4 stars, last pushed 3mo ago), licensed MIT. It adds 1,342 tokens to every session, about $0.0067 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
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.
Kanvas AGENTS.md
Instructions for XMihura/Kanvas, covering canvas workflow — agent instructions, critical rule, session protocol, 1. start of session — read the board and 2. pick a task.
delivery-loop CLAUDE.md
Instructions for blakemartz/delivery-loop, covering claude.md, what this is, the cardinal rule: everything must stay repo-agnostic, layout and config: the one seam.
taskcenter AGENTS.md
AGENTS.md instructions for xiaogezi/taskcenter, covering taskcenter agent rules, safety boundaries, required workflow and verification.
idd-skill idd-resume.instructions.md
Instructions for kurone-kito/idd-skill, covering idd — resume phase, required inputs, step 0 — route classifier, operator-present release and step 1 — identify claim state.
kanban-lite AGENTS.md
AGENTS.md instructions for borgius/kanban-lite, covering kanban markdown - development guide, repo-wide defaults and post-change verification (mandatory).