Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add fortunto2/solo-factory/plugin install soloWrote 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/fortunto2/solo-factory/memory-audit)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/memory-audit"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/memory-audit/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/fortunto2/solo-factory/memory-audit"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/memory-audit.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.00045 | $0.01084 |
| Opus 5 | $0.00023 | $0.00542 |
| Sonnet 5 | $0.00009 | $0.00217 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
solo-memory-audit 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 9d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/memory-audit
Audit Claude Code memory hierarchy for a project. Shows what files load at session start, total context budget, and optimization hints.
Context
Claude Code loads memory files at session start in this order:
- Managed policy (
/Library/Application Support/ClaudeCode/CLAUDE.md) - User memory (
~/.claude/CLAUDE.md) - User rules (
~/.claude/rules/*.md) - Auto-memory (
~/.claude/projects/{key}/memory/MEMORY.md, first 200 lines) - Project hierarchy (walk from
/to CWD:CLAUDE.md,.claude/CLAUDE.md,.claude/rules/*.md) - Local overrides (
CLAUDE.local.mdat each level)
Rules with paths: frontmatter are conditional — loaded only when working on matching files. Rules without paths: always load and consume context budget.
Target: keep startup context under 40k chars. Large CLAUDE.md files should extract domain-specific sections into conditional .claude/rules/*.md files.
Steps
-
Determine target. Parse
$ARGUMENTS:- Empty or
.-> use CWD - Path -> use that path
all-> scan CWD subdirectories that have CLAUDE.md
- Empty or
-
Run memory_map.py. Execute:
uv run python ${CLAUDE_PLUGIN_ROOT}/scripts/memory_map.py <path> --auditIf
allargument, add--all-projectsflag instead of path.If
uvis not available, fall back to:python ${CLAUDE_PLUGIN_ROOT}/scripts/memory_map.py <path> --audit --plain -
Analyze the output. Read the tree display and audit hints table. Key metrics:
- Total startup chars — should be under 40k
- Large files (>300 lines) — candidates for splitting into rules
- Unconditional rules (>30 lines, no
paths:frontmatter) — addpaths:to make conditional - Duplicate sections — same
## Headerin multiple files, extract to one place - Missing auto-memory — project doesn't learn across sessions
-
Generate recommendations. Based on audit hints, suggest concrete actions:
Issue Action File > 300 lines Extract domain sections to .claude/rules/{topic}.mdwithpaths:frontmatterTotal > 40k chars Identify largest files, move conditional content to rules Unconditional rule > 30 lines Add paths:frontmatter targeting relevant source filesDuplicate sections Keep in the highest-level file, remove from children No auto-memory Normal for new projects, just informational User-level rule is project-specific Move from ~/.claude/rules/to project's.claude/rules/Generic rule in project Move up to ~/.claude/rules/or parent CLAUDE.md
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.
- 9d ago First seen · 112 lines · 45 tokens per session scan A bf8ae0fd28c5
solo-memory-audit is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 1,084 once invoked, about $0.0002 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-30.
Other skills, from other repositories
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
last30Days
Resolve "last30Days" to a concrete ISO date range relative to your run time — a rolling 30-day window ending today. Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a "last 30 days" / trailing-month task…
thisWeek
Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…
comet-memory
A review step for deciding whether information should become durable personal memory. It can keep, update, forget, or skip memory candidates based on bounded evidence.
mnemos
Task-scoped memory lifecycle — typed MnemoGraph prevents lossy context compaction by treating facts/decisions/code-refs/handoffs as distinct node types with per-type eviction policies.