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.
git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-MonitorWrote 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/commands/hoangsonww/claude-code-agent-monitor/memory)<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/memory"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/memory/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.
<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/memory"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/memory.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00504 |
| Opus 5 | $0.00010 | $0.00252 |
| Sonnet 5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
memory 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:4820/api/cc-config/memory What it actually says
List the user's file-based memory store from the Agent Monitor Config Explorer
at http://localhost:4820. If $ARGUMENTS is given, treat it as a
project-slug filter and show only matching auto-memory groups.
curl -s http://localhost:4820/api/cc-config/memory
The response is { items: [...] }. Two kinds of entry:
- CLAUDE.md —
{ scope:"user"|"project", file, size, mtime, preview }. - Auto-memory facts —
{ scope:"auto-memory", project, name, isIndex, file, size, mtime, frontmatter, preview }.
Print in two parts:
-
CLAUDE.md — one line per entry:
scope,size(KB), last-modified. Flag any withtruncated: trueas oversized. -
Auto-memory, grouped by
project— for each project (filtered by$ARGUMENTSif provided), list the index file (isIndex: true, usuallyMEMORY.md) first, then each per-fact file withname,frontmatter.description(or start ofpreview),size(KB), andmtime.
Memory store
CLAUDE.md
user ..... 8.2 KB modified 3d ago
project .. 1.1 KB modified 1h ago
Project: -Users-david-WebstormProjects-foo (4 files)
MEMORY.md (index) ......... 0.6 KB
feature_x_decision.md ..... 0.3 KB — "why we chose X over Y"
api_quirk.md .............. 0.2 KB — "endpoint Z returns 200 on error"
Cite only fields the API returned — never invent facts, names, or sizes. Note
that auto-memory files are editable via PUT/DELETE /api/cc-config/file
(a backup is taken automatically) but this command is read-only. If the
dashboard is unreachable, say so and tell the user to start it with npm start
from the repo root.
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.
- 10d ago First seen · 46 lines · 21 tokens per session scan A e278e6160961
memory is a command published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (987 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 504 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
lessons-compact
Compact MEMORY/LESSON.md by deduplicating near-identical lessons, merging same-root-cause lessons, and pruning stale ones — without losing any unique signal. Delegates the analysis to the lessons-compactor agent.
lessons
View project lessons in MEMORY/LESSON.md (project root) and append a compact "never reproduce" lesson.
cleanup-context
Memory optimization - removes duplicates, consolidates knowledge, and cleans memory banks for better performance.
apex
APEX Methodology - The systematic Analyze-Plan-Execute-eLicit-eXamine approach for intelligent development. Reduces hallucination and defect risk through mandatory parallel research, self-review, and validation gates.
explain-architecture
Analyze and explain software architecture with ASCII diagrams and pattern detection. Creates visual representations of system design.
reflect
Capture learnings from the current conversation through guided reflection.