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 KumihoIO/kumiho-plugins/plugin install kumiho-memoryWrote 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/kumihoio/kumiho-plugins/kumiho-backfill)<a href="https://agentmods.dev/commands/kumihoio/kumiho-plugins/kumiho-backfill"><img src="https://agentmods.dev/badge/commands/kumihoio/kumiho-plugins/kumiho-backfill/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/kumihoio/kumiho-plugins/kumiho-backfill"><img src="https://agentmods.dev/badge/commands/kumihoio/kumiho-plugins/kumiho-backfill.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.02042 |
| Opus 5 | $0.00010 | $0.01021 |
| Sonnet 5 | $0.00004 | $0.00408 |
| Haiku 4.5 | $0.00002 | $0.00204 |
Grade A, and why
kumiho-backfill 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kumiho History Backfill
Mine the user's existing Claude Code session transcripts into ontology-typed
memories so the graph knows their work from day one. Two stages, decoupled by
a local staging file (~/.kumiho/backfill/staging.json): extract (local
only, nothing uploaded) and ingest (uploads only after the user reviews
the exact payload). Design: docs/BACKFILL_DESIGN.md in kumiho-plugins.
If the argument is extract or ingest, run only that stage. Default: both.
Sources. scan/manifest auto-discover Claude Code (~/.claude/projects)
and Codex CLI (~/.codex/sessions); pass --source claude|codex|all
(default all) to narrow. A ChatGPT history is a user-supplied data export —
if the user has one, add --chatgpt-export /path/to/conversations.json to
scan/manifest. All three flow through the same distill → review → ingest
pipeline and land as source:<tool>-tagged, ontology-typed memories.
All scripts live at ${CLAUDE_PLUGIN_ROOT}/scripts/; if CLAUDE_PLUGIN_ROOT
is unset, use the plugin directory relative to this file. Below, INV means:
python "${CLAUDE_PLUGIN_ROOT}/scripts/backfill_inventory.py"
Stage 1 — Extract (local only)
-
Scan + consent. Run
INV scan. Show the user the full output — including the processing disclosure — and ask which projects to include (all, or a subset; pass--projects a,bbelow). Wait for their answer. -
Manifest + packets. Run
INV manifest [--projects ...], thenINV packetize(default top-25; honor a user-requested size). Packets are pre-anonymized excerpts at~/.kumiho/backfill/packets/<session-id>.md. -
Distill each packet (this is your job — no other LLM is involved). Read one packet at a time and produce a captures file, then record it:
INV stage --session <session-id> --captures-file /tmp/<session-id>.jsonThe captures file is
{"captures": [...], "decompose": {...}}where every capture hastype,title,content,event_date,space_hint, and optionalevidence.
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.
- 7d ago Changed c37074e0e33d
- 12d ago First seen · 154 lines · 21 tokens per session scan A 53ae9d6aa054
kumiho-backfill is a command published in the GitHub repository KumihoIO/kumiho-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 2,042 once invoked, about $0.0001 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-31.
Other commands, from other repositories
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.