Memori MCP Memory Usage
MemoriLabs/Memori
Teaches an MCP-connected agent when and how to call Memori's recall, summary, compaction, augmentation, feedback and quota tools to keep context across sessions.
Lists recent sessions on the current project from other agents such as Claude Code, OpenClaw and Copilot CLI, or from your own earlier work.
Install TMA1 Peer Sessions
$ npx skills add tma1-ai/tma1 --skill tma1-peer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tma1-ai/tma1 tma1-peer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tma1-ai/tma1.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-plugin/codex-skills/tma1-peer .claude/skills/tma1-peer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "tma1-peer" agent skill from https://github.com/tma1-ai/tma1/tree/main/claude-plugin/codex-skills/tma1-peer into .claude/skills/tma1-peer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tma1-peer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tma1-ai/tma1/tree/main/claude-plugin/codex-skills/tma1-peerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tma1-ai/tma1 --skill tma1-peer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tma1-ai/tma1 tma1-peer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tma1-ai/tma1.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude-plugin/codex-skills/tma1-peer .agents/skills/tma1-peer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tma1-peer" agent skill from https://github.com/tma1-ai/tma1/tree/main/claude-plugin/codex-skills/tma1-peer into .agents/skills/tma1-peer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tma1-peer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tma1-ai/tma1 --skill tma1-peer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tma1-ai/tma1 tma1-peer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tma1-ai/tma1.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude-plugin/codex-skills/tma1-peer .cursor/skills/tma1-peer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tma1-peer" agent skill from https://github.com/tma1-ai/tma1/tree/main/claude-plugin/codex-skills/tma1-peer into .cursor/skills/tma1-peer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tma1-peer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tma1-ai/tma1.git --path claude-plugin/codex-skills/tma1-peer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tma1-ai/tma1 --skill tma1-peer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tma1-ai/tma1 tma1-peer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tma1-ai/tma1.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude-plugin/codex-skills/tma1-peer .gemini/skills/tma1-peer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tma1-peer" agent skill from https://github.com/tma1-ai/tma1/tree/main/claude-plugin/codex-skills/tma1-peer into .gemini/skills/tma1-peer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tma1-peer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tma1-ai/tma1 tma1-peerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tma1-ai/tma1 --skill tma1-peer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tma1-ai/tma1.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude-plugin/codex-skills/tma1-peer .github/skills/tma1-peer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tma1-peer" agent skill from https://github.com/tma1-ai/tma1/tree/main/claude-plugin/codex-skills/tma1-peer into .github/skills/tma1-peer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tma1-peer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tma1-ai/tma1 --skill tma1-peer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tma1-ai/tma1 tma1-peer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tma1-ai/tma1.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude-plugin/codex-skills/tma1-peer .opencode/skills/tma1-peer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tma1-peer" agent skill from https://github.com/tma1-ai/tma1/tree/main/claude-plugin/codex-skills/tma1-peer into .opencode/skills/tma1-peer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tma1-peer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
tma1-peer- GitHub stars
- 119
- Token cost
- ~1.3k tokens
- SKILL.md length
- 528 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Lists recent sessions on the current project from other agents such as Claude Code, OpenClaw and Copilot CLI, or from your own earlier work.
- Works in 3 steps: fetchEmits has no LIMIT — body cap will… → applyForceColor env dedup is… → anomalyCache.history map never evicts…
- Reading what Claude Code did on the project before continuing its work
- SKILL.md covers Invocation, Normalize the agent name, Flags and Call the tma1 MCP tool, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Run /tma1-peer to read what another coding agent did on this project, so you can act on its review feedback or context without copying text between terminals. Without arguments it shows the latest session from every peer except you, newest first. Naming an agent narrows it: claude or cc for Claude Code, openclaw, copilot for Copilot CLI, self or me for your own sessions, and all for every peer. An unknown name gets a reply listing the valid ones and no tool call.
Flags set the detail and range: summary gives header, tools and files with no messages, the default preview shows three recent messages, and full shows 40. Limit sets how many sessions per agent, from one to five with a default of one, and since takes values like 2h or 90m with a default window of 1440 minutes.
The skill calls the get_peer_sessions tool on the project's tma1 MCP server and uses the returned sessions directly: session identity, activity times and duration, working directory, tool call and token counts, messages, recent tool names and files touched. This version is written for Codex.
When your agent uses it
- Reading what Claude Code did on the project before continuing its work
- Acting on another agent's review feedback without copy-pasting
- Recalling what you did earlier in the same project
Example prompts
- “What did claude do on this project in the last two hours?”
- “/tma1-peer copilot --full to see its full conversation.”
- “Show my own past sessions here so I can pick up where I left off.”
Requirements
- A TMA1 install that registers the tma1 MCP server for the project
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- fetchEmits has no LIMIT — body cap will truncate before the query finishes.
- applyForceColor env dedup is libc-dependent.
- anomalyCache.history map never evicts stale sessions.
What it can do on your machine
Read from SKILL.md and the folder at commit f3dfed8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
TMA1 Peer Sessions loads about 1.3k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 528 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from tma1-ai/tma1 at commit f3dfed8, republished under its Apache-2.0 licence (© tma1-ai). 528 words, ~1,307 tokens.
Download SKILL.mdSave it as
.claude/skills/tma1-peer/SKILL.md (or your agent's skills folder).- name
- tma1-peer
- description
- List recent sessions on this project by agent — peers (Claude Code, OpenClaw, Copilot CLI) or your own past sessions. Invoke this skill when the user asks you to read another agent's review feedback, see what someone else tried, act on cross-agent context, or recall your own earlier work here. Trigger phrases: "what did claude do", "what did openclaw do", "what did copilot do", "peer sessions", "cross-agent context", "what did I do earlier", "/tma1-peer".
TMA1 Peer-Agent Lens (Codex)
Lists recent sessions on the current project, newest first. Default is peer agents — the ones that aren't you — because the usual reason to call this is "Claude Code or Copilot left something here, act on it without me copy-pasting between terminals". Naming yourself is also allowed.
Invocation
Auto-selected when the user mentions reading another agent's output on this project, or typed explicitly:
/tma1-peer # all peers, latest session each
/tma1-peer claude # Claude Code only
/tma1-peer claude --full # with full conversation content
/tma1-peer self # your own recent sessions here
/tma1-peer copilot --limit 2 # latest 2 Copilot CLI sessions
/tma1-peer --summary --limit 5 # headers only, 5 per agent
/tma1-peer claude --since 6h # widen the time windowNormalize the agent name
| Input | agent_source to send |
|---|---|
claude, cc | claude_code |
claude_code | claude_code |
openclaw | openclaw |
copilot | copilot_cli |
self, me | self (the server resolves it) |
all, *, empty | "" (every peer except you) |
Any other value: reply
unknown agent "<X>"; available: claude, openclaw, copilot, self, all
and STOP — do not call the tool with an unrecognised name.
Flags
| Flag | Argument to send | Default |
|---|---|---|
--summary | detail: "summary" — header, tools, files; no messages | |
| (none) | detail: "preview" — 3 recent messages | default |
--full | detail: "full" — 40 recent messages | |
--limit N | limit — sessions per agent, [1, 5] | 1 |
--since 2h / --since 90m | since_min in minutes | 1440 |
Legacy positional form [agent] [limit] [message_limit] still works; a
bare leading integer is the limit, not an agent.
Call the tma1 MCP tool
This project's TMA1 install registers an MCP server named tma1. Call
its get_peer_sessions tool with the parsed arguments. If your runtime
addresses MCP tools by a prefixed name (tma1.get_peer_sessions,
mcp_tma1_get_peer_sessions), use whichever convention this Codex
install uses — it's the same tool.
Use the returned content directly
sessionsarray — identity (session_id,agent_source,started_at,last_activity_at,last_activity_ago,duration_minutes,cwd), volume (tool_call_count,tokens_input,tokens_output), content (messages,recent_tool_names,files_touched). On aselflookup,is_latest_for_cwdmarks the session you are almost certainly in right now — don't report your own current work back as news.most_recent_session— freshest session's agent + age; lead with it.partial_failures—agent → error_message, present only when the all-peers fan-out had a failure. Check it before treating emptysessionsas "no peer activity".
When you act on what the peer left:
- Quote concrete points the peer made. Don't paraphrase — the user wants the peer's exact feedback in your context, not your summary.
- List the files the peer touched, when the next step is "fix what they flagged".
- Surface the timing. "Claude left this 12 min ago" beats "recently".
- A message with
truncated: truewas cut to fit; fetch the rest with theget_session_transcripttool for thatsession_id.
Show full SKILL.md (149 more words)Show less
If sessions is empty and partial_failures is absent, reply
no recent <agent> sessions on this project in the active window and
stop — do not fabricate context. If partial_failures is present, quote
the failed agent(s) instead of asserting silence.
Related tools
- Searching by keyword instead of by agent → the
tma1-searchskill (search_sessions). - Already holding a
session_id→get_session_transcript.
Examples
User: "what did claude leave on this project?"
You: (call get_peer_sessions with agent_source: "claude_code", detail: "full")
You: "Claude Code reviewed server/internal/handler/anomalies.go 8 minutes ago and flagged three concrete issues:
- fetchEmits has no LIMIT — body cap will truncate before the query finishes.
applyForceColorenv dedup is libc-dependent.- anomalyCache.history map never evicts stale sessions. Want me to address all three or pick one?"
User: /tma1-peer self
You: (call get_peer_sessions with agent_source: "self")
You: "Two of your earlier sessions here today: 14:20 landed the retry fix,
11:05 was the abandoned migration attempt."
© tma1-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in claude-plugin/codex-skills/tma1-peer of tma1-ai/tma1.
Open the folder on GitHubat commit f3dfed8
Compare with similar skills
TMA1 Peer Sessions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| TMA1 Peer Sessions this skilltma1-ai/tma1 | 119 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Memori MCP Memory UsageMemoriLabs/Memori | 17k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Ourmemourmem/omem | 174 | 1 repos | ~3.4k | Automated safety check: Pass | Custom licence | |
| Claude Code Auto-Capture HookNateBJones-Projects/OB1 | 4.7k | — | ~1.3k | Automated safety check: Notes | Custom licence | |
| Memory Searchthedotmack/claude-mem | 99k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Engram MemoryPatdolitse/piia-engram | 163 | — | ~1.3k | Automated safety check: Pass | AGPL-3.0-or-later |
Similar skills
Ourmem
ourmem/omem
Shared memory that never forgets. An agent skill from ourmem/omem.
Claude Code Auto-Capture Hook
NateBJones-Projects/OB1
Fires a Stop hook that captures a Claude Code session transcript automatically when the session ends without a verbal wrap-up.
Memory Search
thedotmack/claude-mem
Searches the claude-mem database of past sessions in layers (index, timeline, full details) to find how a problem was solved before.
Engram Memory
Patdolitse/piia-engram
Routes continuity and recall requests to Engram, a local-first MCP memory and identity layer that saves user-approved lessons, decisions and playbooks.
Compartment Session Sweep
MaxFreedomPollard/Compartment
Sweeps a conversation before compaction and saves durable facts, decisions and session records into the Compartment encrypted memory vault as short one-claim memories.
More from tma1-ai/tma1
TMA1 Peer Sessions
tma1-ai/tma1
Lists recent sessions of peer coding agents such as Codex, OpenClaw or Copilot CLI, or your own past sessions, so you can act on their work without copying between terminals.
TMA1 Session Search
tma1-ai/tma1
Searches past agent sessions on a project by keyword through the TMA1 MCP server and reads back a chosen session so answers can quote it directly.
TMA1 Session Search
tma1-ai/tma1
Searches earlier agent sessions on this project by keyword and reads back a session's conversation, answering with quotes from what was actually said.
TMA1 Observability Query
tma1-ai/tma1
Answers questions about agent spend, token use, traces, events, errors and tool usage by running read-only SQL against a local TMA1 observability store.
Related
Works with
Categories
Questions about TMA1 Peer Sessions
What does TMA1 Peer Sessions do?
Lists recent sessions on the current project from other agents such as Claude Code, OpenClaw and Copilot CLI, or from your own earlier work. Run /tma1-peer to read what another coding agent did on this project, so you can act on its review feedback or context without copying text between terminals. Without arguments it shows the latest session from every peer except you, newest first.
When should I use TMA1 Peer Sessions?
TMA1 Peer Sessions fits situations like: reading what Claude Code did on the project before continuing its work; acting on another agent's review feedback without copy-pasting; recalling what you did earlier in the same project.
How do I install TMA1 Peer Sessions in Claude Code?
Run `npx skills add tma1-ai/tma1 --skill tma1-peer -a claude-code`. Or copy the skill folder (claude-plugin/codex-skills/tma1-peer in tma1-ai/tma1) into .claude/skills/tma1-peer in your project. Claude Code loads it when a task matches its description.
How do I install TMA1 Peer Sessions in Codex?
Run `npx skills add tma1-ai/tma1 --skill tma1-peer -a codex`. Or copy the skill folder (claude-plugin/codex-skills/tma1-peer in tma1-ai/tma1) into .agents/skills/tma1-peer in your project. Codex loads it when a task matches its description.
Can I use TMA1 Peer Sessions in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tma1-ai/tma1 --skill tma1-peer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tma1-peer, .gemini/skills/tma1-peer, .github/skills/tma1-peer and .opencode/skills/tma1-peer in your project.
What does TMA1 Peer Sessions need to run?
SKILL.md names no scripts, command-line tools or credentials: TMA1 Peer Sessions is instructions for the agent only. Our summary lists: A TMA1 install that registers the tma1 MCP server for the project.
Does TMA1 Peer Sessions access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is TMA1 Peer Sessions safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does TMA1 Peer Sessions use?
TMA1 Peer Sessions is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does TMA1 Peer Sessions use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to TMA1 Peer Sessions?
Skills that share tags, products or a category with TMA1 Peer Sessions: Memori MCP Memory Usage (MemoriLabs/Memori, 17k stars), Ourmem (ourmem/omem, 174 stars), Claude Code Auto-Capture Hook (NateBJones-Projects/OB1, 4.7k stars) and Memory Search (thedotmack/claude-mem, 99k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains TMA1 Peer Sessions?
tma1-ai (a GitHub organization) maintains it in tma1-ai/tma1, which has 119 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.
Source: tma1-ai/tma1 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.