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/bdiasti/maestro-bundle-cli/memory-managementnpx skills add bdiasti/maestro-bundle-cli --skill memory-managementgit clone --depth 1 https://github.com/bdiasti/maestro-bundle-cliWrote 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/bdiasti/maestro-bundle-cli/memory-management)<a href="https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/memory-management"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/memory-management.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.00044 | $0.01517 |
| Opus 5 | $0.00022 | $0.00758 |
| Sonnet 5 | $0.00009 | $0.00303 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
memory-management 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 3d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Management
Implement three tiers of agent memory -- short-term (context window), medium-term (checkpointer), and long-term (store) -- to enable persistent learning and state management.
When to Use
- Agent needs to resume work after interruption
- Agent should learn from past executions and avoid repeating mistakes
- Persisting state between nodes in a LangGraph workflow
- Storing and retrieving patterns learned across multiple demands
- Implementing memory decay to remove stale or low-confidence knowledge
Available Operations
- Configure short-term memory via context window
- Set up medium-term memory with LangGraph checkpointer
- Implement long-term memory with LangGraph Store
- Integrate memory into Deep Agent configuration
- Implement memory cleanup and decay policies
Multi-Step Workflow
Step 1: Set Up Short-Term Memory (Context Window)
Short-term memory is automatic -- LangGraph accumulates messages within a session.
from typing import TypedDict, Annotated
from langgraph.graph.message import add_messages
class AgentState(TypedDict):
messages: Annotated[list, add_messages] # Accumulates automatically
No additional setup needed. Messages persist for the duration of a single invocation chain.
Step 2: Set Up Medium-Term Memory (Checkpointer)
Persists graph state between invocations of the same demand. Enables resume after failure.
pip install langgraph-checkpoint-postgres psycopg
from langgraph.checkpoint.postgres.aio import AsyncPostgresSaver
from langgraph.graph import StateGraph
checkpointer = AsyncPostgresSaver.from_conn_string(DATABASE_URL)
graph = StateGraph(OrchestratorState)
# ... define nodes and edges ...
app = graph.compile(checkpointer=checkpointer)
# Use consistent thread_id per demand
config = {"configurable": {"thread_id": f"demand-{demand_id}"}}
result = await app.ainvoke({"messages": [...]}, config=config)
# Next invocation with same thread_id resumes from saved state
result2 = await app.ainvoke({"messages": [new_msg]}, config=config)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 191 lines · 44 tokens per session scan A 978a4cbe042a
memory-management is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 1,517 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…