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 agentmods add skills/gentech-labs/gentech-agent-kit/memory-tieringnpx skills add Gentech-Labs/genTech-agent-kit --skill memory-tieringgit clone --depth 1 https://github.com/Gentech-Labs/genTech-agent-kitWrote 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/gentech-labs/gentech-agent-kit/memory-tiering)<a href="https://agentmods.dev/skills/gentech-labs/gentech-agent-kit/memory-tiering"><img src="https://agentmods.dev/badge/skills/gentech-labs/gentech-agent-kit/memory-tiering.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.00816 |
| Opus 5 | $0.00008 | $0.00408 |
| Sonnet 5 | $0.00003 | $0.00163 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
memory-tiering 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 4d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Tiering — Intelligence for Intelligence
Jordan's model (Aug 20, 2026): an agent's always-loaded memory (MEMORY.md / USER.md) should NOT be a dump. It should be a curated index of the facts we touch every session, with everything else parked in the vault brain where it's one search away.
When to Use
- Before saving a NEW durable fact to persistent memory.
- When pruning / consolidating MEMORY.md or USER.md (including via the fleet dietician).
- When you notice a memory file approaching the 85% threshold.
- When a fact becomes RESOLVED and you decide whether to keep it loaded.
Two tiers:
- Always-loaded (MEMORY.md / USER.md) — facts referenced EVERY session. Identity, rails, wallet, rules, standing strategy. Lean, high-signal.
- Vault brain (retrievable) — facts referenced less often, or RESOLVED. Not lost, just parked. Pull back via session_search / search_files when the topic resurfaces.
Why (the intelligence part)
- Every session reads the memory file. Bloat = slower, more tokens, worse focus.
- More memory = worse performance (proven Jul 28, 2026: elaborate memory stack deleted → agent worked dramatically better).
- Trimming from the BACK (oldest-first) is dumb — an old high-frequency fact gets archived while a recent resolved worry stays loaded. Tier by relevance, not age.
Tiering rules
ALWAYS-LOADED (keep in MEMORY.md/USER.md)
- Identity: who the agent is, personality, speech, the boss.
- Core rails/keys: payment rails, wallets, canonical repos, the strategy that shapes every decision.
- Standing rules/red lines: "never fake receipts," "spend less," "flag blockers immediately," "build first talk later."
- Recurring topics (per Jordan Aug 20): agentic treasury, x402, AWS, APIs.
- Active commitments with near deadlines.
ARCHIVES TO VAULT BRAIN (low-frequency / resolved)
- Resolved worries: problem solved, deadline passed, task done. Compress or archive.
- One-off events: a single completed hackathon/hire/date.
- Task progress / session logs: go to the brain (Green Room / Mess Hall / handoffs), NOT persistent memory.
- Any fact not touched in many sessions and not needed for the standing model.
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.
- 4d ago First seen · 69 lines · 15 tokens per session scan A 89127f3bba43
memory-tiering is a skill published in the GitHub repository Gentech-Labs/genTech-agent-kit (0 stars, last pushed 13d ago), licensed MIT. It adds 15 tokens to every session and 816 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 skills, from other repositories
context-manager
Context management skill providing discovery, fetching, harvesting, extraction, compression, organization, cleanup, and guided workflows for project context.
project-wiki
组织和维护 Vibe Coding 项目的 wiki 文档体系。当用户要求初始化/重构 wiki 结构、进入新项目且 wiki/ 不存在、需要诊断和修复文档腐化、或需要管理 specs/refs/reviews 子目录的生命周期时触发。.
mindos-zh
MindOS 是用户的本地知识助手，也是跨会话、跨 Agent 共享的知识库。它保存决策记录、会议纪要、SOP、 排错经验、架构选型、调研结论和偏好设置。 仅 mindRoot 知识库内任务。不用于：改代码仓库、项目源码、KB 外路径。 核心概念：空间、指令(INSTRUCTION.md)、技能(SKILL.md)；笔记可承载指令与技能。 触发场景：保存或记录任何内容、搜索历史笔记或上下文、更新或编辑文件、整理或重组文件结构、 执行SOP或工作流、捕获对话中的决策、复盘或总结经验、追加表格或CSV数据、跨Agent交接上下文、 提炼经验教训、同步关联文档、查找之前是否讨论过某事、查询历史决策、查找模板或SOP、…
mindos
MindOS: local knowledge assistant & shared KB. Keeps decisions, notes, SOPs, debugging lessons, research findings, preferences across sessions/agents. Core: save notes, search KB, organize files, run workflows, review, append CSV, hand off context, distill lessons. NOT for app source or paths outside KB. Triggers…
mindos-max
MindOS: local knowledge assistant & global memory layer. Keeps decisions, notes, SOPs, debugging lessons, architecture choices, research findings, preferences, conversation summaries for all connected agents. PROACTIVE: (1) search MindOS first for past context, (2) offer to save after valuable work, (3) persist key…
mindos
Operate a MindOS knowledge base: update notes, search, organize files, execute SOPs/workflows, retrospective, append CSV, cross-agent handoff, route unstructured input to the right files, distill experience, sync related docs. Use when the task targets files inside the user's MindOS KB (mindRoot). NOT for editing app…