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 tomzx/agents --skill kb-organized-memorygit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/kb-organized-memory)<a href="https://agentmods.dev/skills/tomzx/agents/kb-organized-memory"><img src="https://agentmods.dev/badge/skills/tomzx/agents/kb-organized-memory/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/tomzx/agents/kb-organized-memory"><img src="https://agentmods.dev/badge/skills/tomzx/agents/kb-organized-memory.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.00051 | $0.01437 |
| Opus 5 | $0.00026 | $0.00718 |
| Sonnet 5 | $0.00010 | $0.00287 |
| Haiku 4.5 | $0.00005 | $0.00144 |
Grade A, and why
kb-organized-memory 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 6d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack channel knowledge base — organized by theme
Use when creating or updating cross-month, theme-centric documentation for any Slack channel you maintain in this repo, derived from temporal monthly files.
Per channel, fix a stable <channel-slug> (short kebab-case id, same string as in slack-kb-channel temporal filenames). Know the Slack channel id (C…) when you need to align with ingestion or disambiguate threads.
Inputs (read-only)
- Source of truth (temporal):
memory/temporal/<channel-slug>-YYYY-MM.md— one file per month; time-sliced channel digest. - Optionally use
thread-fetch-YYYY-MM-<CHANNEL_ID>.jsonlorextracted-thread-ts-YYYY-MM-<CHANNEL_ID>-valid.txtundermemory/temporal/only for maintainer validation; do not paste thread indexes into organized output.
Do not treat raw Slack export folders or per-thread dumps as inputs for the organized KB.
Outputs (canonical for “by theme”)
Write one markdown file per theme under memory/organized/<channel-slug>/ — not a single monolithic file. Use kebab-case filenames and meaningful theme names.
Theme index: The authoritative map of which files exist and what each covers is memory/organized/<channel-slug>/README.md (table of themes + links). Read it before merging or restructuring; update it whenever you add, remove, rename, or split files. Do not duplicate that catalog in this skill — keep it in memory only.
New files: Add a .md file when a genuinely new theme appears, when an existing file is overloaded (hard to scan or mixed concerns), or when a topic deserves a dedicated home. Prefer one clear theme per file over stuffing unrelated bullets into the nearest match.
Restructuring and moves: You are not limited to appending to existing files. When appropriate:
- Split a file into two (or more) theme files; leave a short pointer in the original if readers might still look there, or rename the original and add redirects in
README.mdonly (avoid broken links in other repos). - Move bullets between theme files when the better home is obvious (e.g. vendor A batch auth notes belong under vendor A even if they were first filed under inference).
- Rename a file only when the theme boundary changed (use kebab-case; update
README.mdand any in-repo links to the old path).
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.
- 6d ago First seen · 67 lines · 51 tokens per session scan A e0cbc898acf3
kb-organized-memory is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,437 once invoked, about $0.0003 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-09-03.
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.