Borrowing it
Nothing to install: this file belongs to Foxfire1st/agents-remember. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Foxfire1st/agents-remember/main/.agents/skills/c-10-adopt-memory-baseline/SKILL.mdgit clone --depth 1 https://github.com/Foxfire1st/agents-rememberWrote 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/foxfire1st/agents-remember/c-10-adopt-memory-baseline)<a href="https://agentmods.dev/skills/foxfire1st/agents-remember/c-10-adopt-memory-baseline"><img src="https://agentmods.dev/badge/skills/foxfire1st/agents-remember/c-10-adopt-memory-baseline.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.00715 |
| Opus 5 | $0.00020 | $0.00358 |
| Sonnet 5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
c-10-adopt-memory-baseline 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 8d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
c-10-adopt-memory-baseline Adopt Memory Baseline
Use this skill when an external memory repo already contains onboarding content and the developer wants to create the initial memory.md ledger from that content.
This skill does not decide that stale onboarding is true. It makes the trust boundary explicit: the c-02-memory-quality-control skill's drift is checked first, and actionable drift blocks adoption unless the developer explicitly accepts the current onboarding as the baseline.
MCP Tools
Use the Agents Remember MCP memory baseline tools as the normal installed runtime entry point:
Preview first.
memory_baseline_adoptnow applies by default. Call it once withdry_run=trueto preview, confirm, then run the real apply (omitdry_run).
memory_baseline_status(repo_id="<repo-id>")
memory_baseline_adopt(repo_id="<repo-id>", accept_drift=false, dry_run=true) # preview
memory_baseline_adopt(repo_id="<repo-id>", accept_drift=true) # apply
Use memory_baseline_status first. Use memory_baseline_adopt only after the
developer approves the baseline decision. The skill tree is instruction-only;
installed and development workflows use the MCP/package route.
Workflow
- Resolve the code repository with the
c-08-ar-coordination-context-resolverskill and confirm external topology. - Run the
c-02-memory-quality-controlskill's drift classification against the resolved onboarding root; its reusable report is written under thec-08-ar-coordination-context-resolverskill's resolved temp root. - Inspect the external memory repo for an existing
memory.md. - If a ledger already exists, report it and stop.
- If drift has actionable findings, stop unless
accept_drift=trueis part of the approvedmemory_baseline_adoptrequest. - Bootstrap the memory repo through the
c-09-git-worktree-managerskill so the existing onboarding/system/docs content becomes the memory content commit andmemory.mdmaps current code HEAD to that memory commit.
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.
- 8d ago First seen · 54 lines · 40 tokens per session scan A 4b1547f10078
c-10-adopt-memory-baseline is a skill published in the GitHub repository Foxfire1st/agents-remember (27 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 715 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
obsidian-memory
Cross-project long-term memory over an Obsidian brain vault: recall relevant notes before a task, and persist distilled conclusions (decisions, pitfalls, solutions, progress) back after a task. The vault is an optional aggregation/projection layer — repo-local artifacts stay the per-project source of truth, and sync…
memwal
Walrus Memory SDK — portable agent memory that works across apps, sessions, and workflows. Use when users say: "add memory to my app" "portable agent memory" "integrate Walrus Memory" "AI agent memory" "memory across agents" "Walrus memory storage" "setup Walrus Memory" "recall memories".
cortex-automate
Set up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to…
cortex-remember-global
Store a global memory that is visible across all projects. Use when the user shares architecture rules, coding conventions, infrastructure facts, security policies, team agreements, or any knowledge that applies beyond a single project. Triggers on 'remember this everywhere', 'this applies to all projects', 'global…
cortex-consolidate
Run memory maintenance — decay old memories, compress stale content, consolidate episodic memories into semantic knowledge, and run sleep-like replay. Use when the user says 'clean up memories', 'consolidate', 'run maintenance', 'compress old memories', 'memory cleanup', or periodically to keep the memory system…
cortex-explore-memory
Explore the memory system's state, find gaps in knowledge, assess coverage, and get diagnostic information. Use when the user asks 'what does my memory look like', 'show me memory stats', 'what am I missing', 'how good is my knowledge', 'memory health', 'show coverage', 'find gaps', 'what topics are weak', or when you…