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 skills add hifriendbot/cogmemai-mcp --skill remember-thisgit clone --depth 1 https://github.com/hifriendbot/cogmemai-mcpWrote 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/hifriendbot/cogmemai-mcp/remember-this)<a href="https://agentmods.dev/skills/hifriendbot/cogmemai-mcp/remember-this"><img src="https://agentmods.dev/badge/skills/hifriendbot/cogmemai-mcp/remember-this/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/skills/hifriendbot/cogmemai-mcp/remember-this"><img src="https://agentmods.dev/badge/skills/hifriendbot/cogmemai-mcp/remember-this.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.00092 | $0.01024 |
| Opus 5 | $0.00046 | $0.00512 |
| Sonnet 5 | $0.00018 | $0.00205 |
| Haiku 4.5 | $0.00009 | $0.00102 |
Grade A, and why
remember-this 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 11d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remember This with CogmemAi
When the user explicitly tells you to remember something, save it to CogmemAi immediately. Don't wait until the end of the session, don't paraphrase loosely, and don't ask for confirmation. The user has done the hard work of identifying what matters; your job is to persist it correctly.
Trigger Phrases
Save the moment you hear any of:
- "Remember this"
- "Remember that I prefer X"
- "Don't forget X"
- "Make a note that X"
- "Keep this in mind"
- "From now on, X"
- "Going forward, X"
- "Always do X" / "Never do X"
- "Save this for next time"
Also trigger when the user states a stable preference even without an explicit "remember" phrase. For example: "I always use Bun instead of npm" is a preference worth saving even though they didn't say "remember".
How to Save
Use save_memory with:
content— restate the user's fact in one or two complete sentences. Include the why if they gave one. Concrete and self-contained.memory_type— usuallypreferencefor user preferences,decisionfor project decisions,identityfor facts about the user,architecturefor tech-stack facts.importance— usually 7-9 for explicit "remember this" requests. The user flagged it as important, respect that signal.scope—globalif the fact applies across all projects (user preference, identity, tool choice).projectif it's specific to the current codebase.tags— short labels so related memories cluster (e.g.,["coding-style"],["deployment"],["communication"]).
Examples
"Remember I'm allergic to em dashes"
save_memory({
content: "User has a strict no-em-dash rule. Never use the em dash character (—, U+2014) in any output: chat replies, code comments, docs, commit messages, marketing copy. Use a comma, parentheses, period and new sentence, colon, or semicolon instead.",
memory_type: "preference",
importance: 9,
scope: "global",
tags: ["writing-style", "punctuation"]
})
"From now on, deploy via Cloud Run not Lambda"
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.
- 11d ago First seen · 97 lines · 92 tokens per session scan A f5dcbeda086d
remember-this is a skill published in the GitHub repository hifriendbot/cogmemai-mcp (7 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 1,024 once invoked, about $0.0005 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
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
mnemos
Task-scoped memory lifecycle — typed MnemoGraph prevents lossy context compaction by treating facts/decisions/code-refs/handoffs as distinct node types with per-type eviction policies.
grimoire
Use when the user says 'update context', 'update claude', 'save library', or after significant project changes.
keep-the-why
Extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup and maintainer interviews. Not for what changed (see Keep a Changelog) - only why. Also the place for complaints, feedback and settings changes about this skill itself.
ln-31-performance-optimizer
Profiles and improves a measured latency, throughput, CPU, memory, or I/O problem. Not for speculative tuning or cosmetic refactoring.