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 skills add hoangsonww/Claude-Code-Agent-Monitor --skill memory-reviewgit 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/skills/hoangsonww/claude-code-agent-monitor/memory-review)<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/memory-review"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/memory-review/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/skills/hoangsonww/claude-code-agent-monitor/memory-review"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/memory-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 66 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00093 | $0.01003 |
| Opus 5 | $0.00046 | $0.00502 |
| Sonnet 5 | $0.00019 | $0.00201 |
| Haiku 4.5 | $0.00009 | $0.00100 |
Grade A, and why
memory-review 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 13d 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 -X PUT http://localhost:4820/api/cc-config/file \ How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Review
Curate the user's file-based agent memory: the long-form CLAUDE.md files plus
the per-project auto-memory store — read through the Agent Monitor dashboard at
http://localhost:4820.
Input
The user provides: $ARGUMENTS
This may be:
- empty — review the whole memory store across every project (default).
- a project slug (e.g.
-Users-david-WebstormProjects-foo) — restrict the review to that one project's auto-memory dir. - "claude-md" — review only the user/project CLAUDE.md files.
Data Sources
| Endpoint | Returns |
|---|---|
GET /api/cc-config/memory |
{ items:[…] }. CLAUDE.md entries: { scope:"user"|"project", file, size, mtime, preview }. Auto-memory entries: { scope:"auto-memory", project, name, isIndex, file, size, mtime, frontmatter, preview } |
GET /api/cc-config/file?path=<abs> |
full body of one file: { ok, file, size, mtime, truncated, text } — use to read a fact in full before recommending an edit |
Report Sections
1. CLAUDE.md overview
List the user and project CLAUDE.md entries with scope, size (KB), and
last-modified (mtime). Note any that are truncated (over 256 KB) — these
are oversized and worth splitting into auto-memory facts.
2. Per-project auto-memory, grouped
Group scope: "auto-memory" items by project. For each project show the
index (isIndex: true, typically MEMORY.md) first, then the per-fact
files. For each fact show name, frontmatter.description if present, size,
and mtime.
3. Index vs per-fact consistency
Within each project, compare the index (MEMORY.md) against the per-fact files
present. Flag facts that exist on disk but are not referenced by the index, and
index entries that point at files which no longer appear in /memory.
4. Stale & oversized facts
Flag facts whose mtime is old relative to the rest of the store (stale —
candidates to confirm or retire) and facts whose size is large (oversized —
candidates to split into smaller, single-fact files). When the user wants to
act on one, fetch its full body with GET /api/cc-config/file?path=<file>
before recommending changes.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago First seen · 92 lines · 93 tokens per session scan A e4582afe79e6
memory-review is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 4d ago), licensed MIT. It adds 93 tokens to every session and 1,003 once invoked, about $0.0005 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 skills, from other repositories
handover
Session handover — end a session by systematically updating project state files for continuity. Use this when the session is ending, the user asks for a "handover", or when significant progress needs to be recorded.
learn
Capture an observation — something that went wrong or worked well — to LEARNINGS.md for future reference. Quick in-session capture, not full analysis.
review-memory
Review auto-memory for the current project. Shows accumulated learnings, identifies noise, and helps promote permanent patterns to CLAUDE.md, rules, or skills.
knowledge-content-routing
Two niche knowledge specialists not covered by existing document-format / documentation skills — Zettelkasten knowledge graph stewardship and enterprise training curriculum design. Use when the user wants to build a Luhmann-style atomic-note knowledge base with connectivity validation, or design a multi-track…
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…
claude-md-updater
Scans the session for lessons and workflows, then proposes scoped CLAUDE.md edits. Use for save this lesson or add to context.