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-11-memory-carryover-from-branch/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-11-memory-carryover-from-branch)<a href="https://agentmods.dev/skills/foxfire1st/agents-remember/c-11-memory-carryover-from-branch"><img src="https://agentmods.dev/badge/skills/foxfire1st/agents-remember/c-11-memory-carryover-from-branch/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/foxfire1st/agents-remember/c-11-memory-carryover-from-branch"><img src="https://agentmods.dev/badge/skills/foxfire1st/agents-remember/c-11-memory-carryover-from-branch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 57 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00037 | $0.01432 |
| Opus 5 | $0.00018 | $0.00716 |
| Sonnet 5 | $0.00007 | $0.00286 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
c-11-memory-carryover-from-branch 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
c-11-memory-carryover-from-branch Memory Carryover From Branch
Use this skill when a protected official code branch receives delayed or batched merges, while a developer has accumulated richer onboarding on another branch. The source branch may be a personal workbench branch, an individual feature branch, or a handpicked branch processed as part of a larger reconciliation pass.
The c-11-memory-carryover-from-branch skill is not a Git merge. It is a selective memory reconciliation step. It proves which source-branch code changes are represented in the official branch, then carries only the corresponding onboarding into an open, external-memory recovery leaf and refreshes verification metadata against the official code commit. That leaf still closes and integrates through the normal journaled code-and-memory lifecycle; carryover never writes an official integration checkout directly.
MCP Tools
Use the Agents Remember MCP memory carryover tools as the normal installed runtime entry point:
memory_carryover_plan(repo_id="<repo-id>", contract_path="<open-recovery-leaf-contract>", source_memory="<source-memory-repo>", official_code_ref="<official-ref>", source_code_ref="<source-ref>", old_base="<base-ref-or-sha>")
memory_carryover_apply(repo_id="<repo-id>", contract_path="<open-recovery-leaf-contract>", source_memory="<source-memory-repo>", official_code_ref="<official-ref>", source_code_ref="<source-ref>", old_base="<base-ref-or-sha>", intent_note="<developer intent>")
Start a dedicated recovery leaf from the landed code-and-memory source pair, then run
memory_carryover_plan against that leaf. Use memory_carryover_apply only after reviewing
the candidate report. Apply mutates only the recovery leaf's ordinary memory worktree; it
does not move code or protected memory refs. Close and integrate the recovery leaf normally.
The skill tree is instruction-only; installed and development workflows use the MCP/package
route.
Candidate Kinds
Candidates are kind-tagged; include_review_required selects each by its selection key.
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 · -3 lines · +3 tokens per session 87afb03a8099
- 12d ago First seen · 77 lines · 34 tokens per session scan A da269842fb3b
c-11-memory-carryover-from-branch is a skill published in the GitHub repository Foxfire1st/agents-remember (27 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,432 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".
lilbee-mcp
Search and manage the user's local lilbee knowledge base over MCP. Use whenever the user has indexed code, docs, PDFs, or web pages into lilbee and you need cited answers, or whenever they ask you to ingest content, swap models, or tune retrieval against their library. Every fact returned cites file and line.…
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-navigate-knowledge
Navigate the knowledge graph — trace entity relationships, explore causal chains, drill into memory clusters, and traverse co-access paths. Use when the user asks 'how are these related', 'what connects X to Y', 'show me the knowledge graph', 'trace the relationship', 'what caused X', 'drill down into', 'explore…
cortex-profile
View and manage your cognitive profile — how you think, work patterns, blind spots, and cross-domain connections. Use when the user says 'show my profile', 'how do I work', 'what are my patterns', 'cognitive style', 'blind spots', 'methodology', or at the start of a session to load context. Also use 'rebuild profile'…