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 emaballarin/ccplugins/plugin install mfWrote 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/emaballarin/ccplugins/dump)<a href="https://agentmods.dev/skills/emaballarin/ccplugins/dump"><img src="https://agentmods.dev/badge/skills/emaballarin/ccplugins/dump/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/emaballarin/ccplugins/dump"><img src="https://agentmods.dev/badge/skills/emaballarin/ccplugins/dump.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.00122 | $0.03458 |
| Opus 5.5 | $0.00049 | $0.01383 |
| Sonnet 5.5 | $0.00024 | $0.00692 |
| Haiku 4.5 | $0.00012 | $0.00346 |
Grade A, and why
dump 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 12d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mf:dump — session → project memory
Write the current session's non-derivable state to the project's auto-memory directory so a future session can resume cleanly. Idempotent: can run mid-session, at a natural checkpoint, or at end-of-session.
Important
- Never proliferate files. Update existing memory first; create new files only when a topic genuinely deserves its own dossier.
- Only log non-derivable signal. Facts recoverable from
git log, current code, orAGENTS.md/PROJECT.mddo not belong in memory. - SOUL.md and the user-global AGENTS.md are sacred. Propose edits, never apply silently, and only when the insight is genuinely general. The user-global AGENTS.md lives at
~/.mindfunnel/AGENTS.md(reached via~/.claude/CLAUDE.md); the per-project./AGENTS.mdis a small project-scoped stub owned by the project — don't treat them as the same file. - Convert every "today" / "tomorrow" to an absolute date before writing. Run
date -Iif uncertain. - Append atomic assertions to the ledger, don't narrate them. Claims, decisions, and learnings that carry a trust level and provenance go to
ledger.jsonl(Step 5b); the narrative stays in Markdown. Never double-log one as the other — cross-reference.
Instructions
Step 1: Locate the memory directory
Use the auto-memory directory Claude Code names in its system prompt. Without one, derive it: ~/.claude/projects/<slug>/memory/, where <slug> is the repository root — shared by its subdirectories and worktrees; $PWD outside git — with every non-alphanumeric character replaced by -. An autoMemoryDirectory setting or CLAUDE_CODE_PROJECT_DIR_NAME overrides the derivation.
bash -c 'g=$(git rev-parse --path-format=absolute --git-common-dir 2>/dev/null) && r=$(dirname "$g") || r=$PWD; echo ~/.claude/projects/$(printf %s "$r" | sed "s/[^A-Za-z0-9]/-/g")/memory'
The directory is usually already created by Claude Code. If not, create it before writing.
Step 2: Verify the project is primed
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.
- 12d ago Changed · +1 lines 2f46d40c8184
- 13d ago Changed f127fd9ee0f5
- 1mo ago First seen · 243 lines · 122 tokens per session scan A 78aabb7f536c
dump is a skill published in the GitHub repository emaballarin/ccplugins (4 stars, last pushed 7d ago), licensed MIT. It adds 122 tokens to every session and 3,458 once invoked, about $0.0005 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-31.
Other skills, from other repositories
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
recall
Recall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.
assigns-audit
Inspect LiveView socket assigns for memory bloat — missing temporaryassigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporaryassigns.
compound-docs
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
context-anchoring
Manage per-feature living documents that capture decisions, constraints, and reasoning across AI sessions during active development. Scoped to feature-level work — design, implementation, bugfix, refactor — not for codebase-wide assessments or product-wide specifications (those define their own document lifecycles).…
learning-harvest
Manage the operational learnings lifecycle — load prior learnings to inform current work, harvest new patterns worth preserving, and keep the document tight over time. Provides a protocol for accumulating actionable patterns from practice that complement standards and defaults. Use when a workflow session completes…