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 joey-barbier/ClaudeCode-Plugin --skill horka-memory-savegit clone --depth 1 https://github.com/joey-barbier/ClaudeCode-PluginWrote 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/joey-barbier/claudecode-plugin/horka-memory-save)<a href="https://agentmods.dev/skills/joey-barbier/claudecode-plugin/horka-memory-save"><img src="https://agentmods.dev/badge/skills/joey-barbier/claudecode-plugin/horka-memory-save/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/joey-barbier/claudecode-plugin/horka-memory-save"><img src="https://agentmods.dev/badge/skills/joey-barbier/claudecode-plugin/horka-memory-save.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.00078 | $0.00768 |
| Opus 5 | $0.00039 | $0.00384 |
| Sonnet 5 | $0.00016 | $0.00154 |
| Haiku 4.5 | $0.00008 | $0.00077 |
Grade B, and why
horka-memory-save scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Use Glob to find `.claude/memory/**/*.md`. How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Save Session Progression
Scope
Updates existing memory files only. Does NOT:
- Create memory files from scratch (use
/horka-memory:horka-memory-restorefor that) - Modify project source code
- Push changes to remote
Step 1: Verify memory exists
Use Glob to find .claude/memory/**/*.md.
If no memory files exist: tell the user "No memory files found. Run /horka-memory:horka-memory-restore first to initialize." and stop.
Read all found files to understand the current documented state.
Step 2: Analyze what happened
Git analysis
Run via Bash:
git log --oneline -20
git status
git diff --stat HEAD~5 HEAD 2>/dev/null || git diff --stat
Conversation analysis
Review the current conversation for:
- Features completed (code written, tested, merged)
- Decisions made (architecture choices, conventions)
- Problems solved (bugs fixed, blockers resolved)
- Files created/modified
- Next steps discussed but not yet done
- Known issues discovered
Step 3: Apply surgical updates
Use Edit for precise changes -- don't rewrite entire files.
PROJECT_STATE.md: Move completed items to DONE, add new completions with detail, remove from TODO, update known issues and key files.
ARCHITECTURE.md: Only update if new modules were created, data flow changed, or dependencies were added.
DECISIONS.md: Add new technical choices with rationale and date:
| Decision | Rationale | Date |
|----------|-----------|------|
| [What] | [Why] | YYYY-MM-DD |
NEXT_STEPS.md: Rewrite priorities based on current state:
## Immediate (next session)
- [ ] Task 1
## Short Term
- [ ] Task 2
## Backlog
- [ ] Task 3
COMMANDS.md: Add any new useful commands discovered.
Step 4: Report
## Memory Saved
**Files updated**:
- PROJECT_STATE.md: [what changed]
- NEXT_STEPS.md: [what changed]
- [other files if modified]
**Session highlights**:
- [Key accomplishment 1]
- [Key accomplishment 2]
**Next session priority**: [Most important next task]
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 · 105 lines · 78 tokens per session scan B 9d551465475e
horka-memory-save is a skill published in the GitHub repository joey-barbier/ClaudeCode-Plugin (22 stars, last pushed 2mo ago), licensed MIT. It adds 78 tokens to every session and 768 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.