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/Yupcha/memXTWrote 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/yupcha/memxt/remember)<a href="https://agentmods.dev/commands/yupcha/memxt/remember"><img src="https://agentmods.dev/badge/commands/yupcha/memxt/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/yupcha/memxt/remember"><img src="https://agentmods.dev/badge/commands/yupcha/memxt/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.00009 | $0.00092 |
| Opus 5.5 | $0.00004 | $0.00037 |
| Sonnet 5.5 | $0.00002 | $0.00018 |
| Haiku 4.5 | $0.00001 | $0.00009 |
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 1mo 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.
What it actually says
Store the following in long-term memory using the memory_store tool, kept verbatim
and concise. If it spans multiple distinct facts, store each as its own memory.
What to remember:
$ARGUMENTS
If no text was given, summarize the most important decision or fact from the current conversation and store that instead. Confirm what you stored in one line.
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.
- 1mo ago First seen · 15 lines · 9 tokens per session scan A cb1fb645f145
remember is a command published in the GitHub repository Yupcha/memXT (49 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 92 once invoked, about $0.0000 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
tl-export
Export thoughtline memories to a markdown file the user can review or commit.
load
Load the shared Wingman context for this project.
tour
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit).
tl-search
Search thoughtline memories by keyword or topickey GLOB.
tl-recent
Show the most recent thoughtline memories for the active project.
tl-stats
Summarize the thoughtline memory store for the active project.