Claude-Code-Agent-Monitor: Instructions file for Claude Code

CLAUDE.md

Claude-Code-Agent-Monitor CLAUDE.md is an instructions file for Claude Code from hoangsonww/Claude-Code-Agent-Monitor. It costs 1,584 tokens per session, scanned A, original, MIT.

Repository instructions for a local dashboard that monitors Claude Code sessions through a server, database, live updates, and a web interface.

In plain words
What is it for?
Use them when working on the dashboard server, React client, session hooks, SQLite data, WebSocket updates, MCP tools, or maintenance commands.
Why use it?
They explain the project layout and rules for preserving monitoring behavior and safety controls while making changes.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

This is hoangsonww/Claude-Code-Agent-Monitor's own configuration. It tells Claude Code how to work on Claude-Code-Agent-Monitor itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Claude-Code-Agent-Monitor configures →

About the project

Claude Code Agent Monitor is a dashboard that records and displays activity from Claude Code and Codex coding-agent sessions, including tool use and subagent coordination. It is for people who need live visibility into agent work through a web interface or native desktop app. The catalogue entries extend Claude Code with skills, commands, agents, plugins, instructions, hooks, and settings related to the monitor.

hoangsonww/Claude-Code-Agent-Monitor · 1,121 stars · on GitHub · hoangsonww.github.io

Reuse

Borrowing it

Nothing to install: this file belongs to hoangsonww/Claude-Code-Agent-Monitor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/hoangsonww/Claude-Code-Agent-Monitor/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor

Made for: Claude Code.

Wrote 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.

agentmods badge for Claude-Code-Agent-Monitor CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/hoangsonww/claude-code-agent-monitor/claude-md/github.svg)](https://agentmods.dev/instructions/hoangsonww/claude-code-agent-monitor/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/hoangsonww/claude-code-agent-monitor/claude-md"><img src="https://agentmods.dev/badge/instructions/hoangsonww/claude-code-agent-monitor/claude-md/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.

agentmods 80×15 button for Claude-Code-Agent-Monitor CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/hoangsonww/claude-code-agent-monitor/claude-md"><img src="https://agentmods.dev/badge/instructions/hoangsonww/claude-code-agent-monitor/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,584 This file is loaded in full into every session.
When invoked 1,584 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01584 $0.01584
Opus 5.5 $0.00634 $0.00634
Sonnet 5.5 $0.00317 $0.00317
Haiku 4.5 $0.00158 $0.00158

Measured 7d ago against content hash 93e953fe788e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Claude-Code-Agent-Monitor 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 7d 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.

CLAUDE.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Claude Code Working Guide

Project mission

  • Maintain a reliable local-first dashboard for Claude Code session monitoring.
  • Preserve real-time behavior (hooks -> API -> SQLite -> WebSocket -> UI).
  • Keep MCP integration production-ready for local use (mcp/).

Repo map

  • server/: Express API, hook ingestion, SQLite access, websocket broadcast (includes optional git upstream checks and routes/updates.js, plus lib/workflow-ingest.js which ingests on-disk Workflow-tool run journals — fleets that emit no hooks).
  • client/: React + Vite UI.
  • scripts/: hook installer/handler, import, seed, cleanup utilities. (Update detection lives server-side in server/lib/update-check.js; the dashboard never restarts itself — users run the printed command, surfaced in the UI and by ccam update-check.)
  • mcp/: local MCP server exposing dashboard operations as tools.
  • cli/: the ccam CLI (Commander.js command tree; bin/ccam.js is the entry). Conventions in cli/lib/framework.js, one module per area in cli/commands/, REPL in cli/repl.js. No subcommand option may reuse a global option name (--json, --format, --server, --token, --no-color) — the root would swallow it; server/__tests__/ccam-cli-framework.test.js enforces this.

Non-negotiable engineering rules

  • Preserve existing behavior unless explicitly asked to change it.
  • Prefer minimal, reversible diffs.
  • Never silently weaken safety controls around destructive actions.
  • Keep docs updated when behavior, commands, file locations, or workflows change — apply the update-project-docs skill automatically at the end of every change-set that alters behavior, config, interfaces, events, schema, CLI commands, or features (do not wait to be asked).
  • Apply the i18n-parity skill whenever a change touches localized content — new/changed UI copy or i18n keys, README-EN.md, a localized full guide, wiki/index.html, or docs the guides and wiki mirror — and work through its new-language checklist whenever adding a language. README.md is an English-only landing page; README-EN.md is the full-guide source of truth. Every supported language ships full-guide changes in the same PR. Verify with bash .claude/skills/i18n-parity/scripts/i18n-audit.sh.
  • Apply the push-to-forked-pr skill whenever updating a PR whose head branch lives on a fork — origin here is the upstream, so a plain git push origin updates the wrong branch and leaves the PR untouched.
  • Apply the version-release skill for every release bump: patch for backward-compatible fixes/small improvements, minor for larger backward-compatible capabilities, and major for breaking/fundamental changes; synchronize root, desktop, OpenAPI, snapshots, and generated plugin metadata, create or reuse the matching v<version> GitHub milestone, and assign the release PR plus linked closing issues to it. The automated workflow input names are major for the first component, intermediate for the middle component, and minor for the last component.
  • Every applicable source file you create or update (.js/.ts/.tsx/.cjs/.mjs/.py/.sh/.css) must start with the copyright/authorship header — file overview + the exact line @author Son Nguyen <[email protected]>. Formats and audit script: .claude/skills/file-headers/ (verify with bash .claude/skills/file-headers/scripts/check-headers.sh). This binds every coding agent (Claude Code, Codex, or others).

Read the full file on GitHub · 61 lines

Changes

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.

  1. 7d ago Changed · +2 lines · +70 tokens per session 93e953fe788e
  2. 16d ago Changed · +19 tokens per session e249fcaa49ea
  3. 22d ago Changed · +1 lines · +70 tokens per session 236fd072133a
  4. 23d ago Changed · +1 lines · +136 tokens per session 14eca24a4830
  5. 1mo ago Changed · +2 lines · +188 tokens per session 282a4f5be73c
  6. 1mo ago First seen · 55 lines · 1,101 tokens per session scan A 60466002b61c

Subscribe to this mod's changes

Claude-Code-Agent-Monitor CLAUDE.md is an instructions file published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (1,121 stars, last pushed 3d ago), licensed MIT. It adds 1,584 tokens to every session, about $0.0063 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens