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.
git clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/remember)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/remember"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/remember/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/yonatangross/orchestkit/remember"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/remember.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.00066 | $0.02242 |
| Opus 5.5 | $0.00026 | $0.00897 |
| Sonnet 5.5 | $0.00013 | $0.00448 |
| Haiku 4.5 | $0.00007 | $0.00224 |
Grade A, and why
remember 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 today.
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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/remember/SKILL.md
Source: https://github.com/yonatangross/orchestkit
Remember - Store Decisions and Patterns
Filesystem vs MCP memory (Opus 5.5 guidance, CC 2.1.111+): Opus 5.5 reads filesystem memory reliably across multi-session work. Use that to your advantage:
- Short-lived handoff state (current phase, task in-progress, pending approvals) →
.claude/chain/*.jsonfiles. Small, structured, session-scoped.- Durable auto-memory (user facts, feedback, project conventions) →
~/.claude/projects/<slug>/memory/*.mdfiles with a one-line index inMEMORY.md. Read on every session start.- Cross-session knowledge graph (typed entities + relations for query traversal) → MCP memory server (this skill's default path). Best when future sessions will search for patterns.
The three are complementary, not alternatives. Prefer fs for anything you'd want to grep; prefer MCP for anything you'd want to traverse.
Store important decisions, patterns, or context in the knowledge graph for future sessions. Supports tracking success/failure outcomes for building a Best Practice Library.
Argument Resolution
TEXT = "$ARGUMENTS" # Full argument string, e.g., "We use cursor pagination"
FLAG = "$ARGUMENTS[0]" # First token — check for --success, --failed, --category, --agent
# Parse flags from $ARGUMENTS[0], $ARGUMENTS[1] etc. (CC 2.1.59 indexed access)
# Remaining tokens after flags = the text to remember
Architecture
The remember skill uses knowledge graph as storage:
- Knowledge Graph: Entity and relationship storage via
mcp__memory__create_entitiesandmcp__memory__create_relations. These tools come from amemoryMCP server that OrchestKit does not bundle: configure one in the user or project scope first (for example@modelcontextprotocol/server-memory) and confirm it withclaude mcp list. Without it, every graph step here does nothing.
Benefits:
- Free and local once the memory server is configured
- Explicit relationship queries (e.g., "what does X use?")
- Cross-referencing between entities
- No cloud dependency
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.
- today Changed 782a158bbac2
- 17d ago Changed b47b06844124
- 21d ago Changed · +4 tokens per session 9088fc4293ad
- 24d ago Changed 9e69233cbbc9
- 1mo ago Changed 68e7082d957f
- 1mo ago Changed 8fa4887e5fb1
- 1mo ago First seen · 215 lines · 62 tokens per session scan A d2e228086891
remember is a command published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 2,242 once invoked, about $0.0003 per session on Opus 5.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 commands, from other repositories
autocompact
Save context to file for automated compact workflow.
memory-shard-roll
Close finished calendar years out of an over-ceiling log-topic file (worklog/support/decisions) into a locked topic-YYYY.md shard, and update the parent's Shards index.
install-attestor
Install Attestor for Claude Code — one default profile, zero questions.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.