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 agentmods add skills/dinhanhthi/coding-friend/cf-remembernpx skills add dinhanhthi/coding-friend --skill cf-remembergit clone --depth 1 https://github.com/dinhanhthi/coding-friendWrote 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/dinhanhthi/coding-friend/cf-remember)<a href="https://agentmods.dev/skills/dinhanhthi/coding-friend/cf-remember"><img src="https://agentmods.dev/badge/skills/dinhanhthi/coding-friend/cf-remember.svg" alt="Measured on agentmods" 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 | $0.00109 | $0.02562 |
| Opus 5 | $0.00055 | $0.01281 |
| Sonnet 5 | $0.00022 | $0.00512 |
| Haiku 4.5 | $0.00011 | $0.00256 |
Grade A, and why
cf-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 5d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cf-remember
CLI Requirement: OPTIONAL — Uses the memory MCP from
coding-friend-clifor fast indexed search and storage. Without the CLI: falls back to grep overdocs/memory/and direct file writes. Full functionality preserved, slower memory recall. See CLI requirements.
Extract and save project knowledge. User input: $ARGUMENTS
Purpose
After a coding session, key knowledge gets lost — logic flows, conventions, decisions, gotchas. This skill captures that knowledge into the project's memory folder so future sessions (and humans) can quickly understand the project.
Folder
Output goes to {docsDir}/memory/ (default: docs/memory/). Check .coding-friend/config.json for custom docsDir if it exists.
IMPORTANT — path resolution:
- Use
MAIN_REPO_ROOTfrom the SessionStart bootstrap context (injected via session-init.sh). If absent, fall back to runningpwdfor$CWDand use$CWDasMAIN_REPO_ROOT. - Read config from
CF_CONFIG_FILE(=$MAIN_REPO_ROOT/.coding-friend/config.json) — do NOT search sub-folders - Use
CF_DOCS_ROOTas the docs base dir (=$MAIN_REPO_ROOT/{docsDir}wheredocsDircomes from config, defaultdocs) - Always resolve
file_pathas an absolute path:{CF_DOCS_ROOT}/memory/{category}/{name}.md - Never use relative paths in write specs — they may resolve incorrectly when the working directory contains nested git repos
Workflow
Step 0: Custom Guide
Custom guide — auto-loaded below (if the raw command shows instead of its output, run it yourself):
bash "<plugin-root>/lib/load-custom-guide.sh" cf-remember
If output is not empty, integrate returned sections: ## Before → before first step, ## Rules → apply throughout, ## After → after final step.
Step 1: Analyze the Conversation
If $ARGUMENTS is provided, use it as a filter — focus only on conversation content that relates to the user's stated purpose. Otherwise, scan the full conversation.
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.
- 5d ago First seen · 233 lines · 109 tokens per session scan A 3d58ca89bb1f
cf-remember is a skill published in the GitHub repository dinhanhthi/coding-friend (3 stars, last pushed today), licensed MIT. It adds 109 tokens to every session and 2,562 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
persist-memory
Persist information to long-term memory at /.clacky/memories/. Use when the user asks you to remember/note something, or when reviewing a finished conversation for facts worth keeping. Handles file naming, topic merging, frontmatter, and size limits.
recall-memory
Recall relevant long-term memories on demand. Given a topic or question, judges relevance from pre-loaded metadata, loads only relevant files, and returns a concise summary to the main agent.
doris-debug-resource-isolation
Use for Doris Workload Group / resource tag queue starvation, CPU/memory isolation leaks, and workload policy debugging. Commands: SHOW WORKLOAD GROUPS, EXPLAIN resource.
remember
Consolidate stashes + friction into project memory.
find-skills
Use when automatically discover, evaluate, and activate community skills when local skills don't cover user needs. Includes credibility scoring and safety checks for complete OpenClaw self-sufficiency.
acontext-installer
Install Acontext, Login & Init Acontext Project, Add Skill Memory to Agent.