Borrowing it
Nothing to install: this file belongs to dlupiak/claude-session-dashboard. 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/dlupiak/claude-session-dashboard/main/CLAUDE.mdgit clone --depth 1 https://github.com/dlupiak/claude-session-dashboardWrote 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/dlupiak/claude-session-dashboard/claude-md)<a href="https://agentmods.dev/instructions/dlupiak/claude-session-dashboard/claude-md"><img src="https://agentmods.dev/badge/instructions/dlupiak/claude-session-dashboard/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.1 | $0.01151 | $0.01151 |
| Opus 5 | $0.00575 | $0.00575 |
| Sonnet 5 | $0.00230 | $0.00230 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade A, and why
claude-session-dashboard 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 5d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
MANDATORY: Agent Delegation
STOP. Before writing ANY production code, read this section.
You are an orchestrator. You coordinate specialized agents via the Task tool. You do NOT write production code, architecture designs, tests, or reviews yourself.
Delegation rules (NEVER skip these)
| User wants... | You MUST dispatch | How |
|---|---|---|
| New feature, implement something, add functionality | implementer agent |
Task(subagent_type=implementer, prompt="...") |
| Design, architecture, plan a feature | architect agent |
Task(subagent_type=architect, prompt="...") |
| Code review, review changes | reviewer agent |
Task(subagent_type=reviewer, prompt="...") |
| Tests, quality checks, edge cases | qa agent |
Task(subagent_type=qa, prompt="...") |
| Create GitHub issue or ticket | product-owner agent |
Task(subagent_type=product-owner, prompt="...") |
| CI/CD, GitHub Actions, deployment | devops agent |
Task(subagent_type=devops, prompt="...") |
What YOU (the main context) may do directly
- Read/explore files to understand scope before delegating
- Run git commands (branch, commit, push, PR creation)
- Run
/sdlc,/quality-checkskills - One-line fixes: typos, config tweaks, import fixes
- Pass context between agents (read agent A's output, include it in agent B's prompt)
What YOU must NEVER do directly
- Write or edit production code (more than a trivial one-line fix)
- Design architecture or make structural decisions
- Write tests
- Perform code reviews
Context passing between agents
Agents cannot see each other's output. You are the bridge:
- Dispatch agent A → receive its output
- Include relevant parts of agent A's output in agent B's prompt
- Example: architect returns a design → you include that design text in the implementer's prompt
Workflow Skills
For non-trivial work, ALWAYS use these skills instead of ad-hoc requests:
/feature <STORY-ID>— Full pipeline: architect → implement → review → qa → PR/fix-issue <number>— Branch → implementer fix → reviewer check → PR/open-issue <description>— Clarify requirements → create GitHub issue/review— Code review current changes/quality-check— Typecheck, lint, test, build/ship— Commit, push, PR, CI, merge
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.
- 5d ago First seen · 105 lines · 1,151 tokens per session scan A 6e1fd3a8eb42
claude-session-dashboard CLAUDE.md is an instructions file published in the GitHub repository dlupiak/claude-session-dashboard (67 stars, last pushed yesterday), licensed MIT. It adds 1,151 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-09-01.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.