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-warmnpx skills add dinhanhthi/coding-friend --skill cf-warmgit 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-warm)<a href="https://agentmods.dev/skills/dinhanhthi/coding-friend/cf-warm"><img src="https://agentmods.dev/badge/skills/dinhanhthi/coding-friend/cf-warm.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.00050 | $0.02581 |
| Opus 5 | $0.00025 | $0.01290 |
| Sonnet 5 | $0.00010 | $0.00516 |
| Haiku 4.5 | $0.00005 | $0.00258 |
Grade A, and why
cf-warm 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cf-warm
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.
Catch up after absence. User input: $ARGUMENTS
Purpose
When you return to a project after being away (vacation, sick leave, context switch), you have no idea what happened. This skill summarizes your recent work and everything the team did since your last commit, grouped by topic/area, so you can quickly get back up to speed.
Folder
Output goes to {docsDir}/warm/ (default: docs/warm/). 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}/warm/YYYY-MM-DD-{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-warm
If output is not empty, integrate returned sections: ## Before → before first step, ## Rules → apply throughout, ## After → after final step.
Step 1: Validate & Configure
- Check git repo — run
git rev-parse --is-inside-work-tree. If it fails, tell the user: "This directory is not a git repository./cf-warmonly works inside git repos." and STOP.
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 · +2 lines a0d6b4bbedb1
- 5d ago First seen · 256 lines · 50 tokens per session scan A 17b0b011e044
cf-warm is a skill published in the GitHub repository dinhanhthi/coding-friend (3 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 2,581 once invoked, about $0.0003 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
cron
Use this skill only for scheduled or recurring tasks. Manage jobs with qwenpaw cron list/create/get/state/update/pause/resume/delete/run, and always pass --agent-id explicitly.
mailbox
当用户需要任何邮箱/邮件操作时使用此技能——包括查看、阅读、搜索、发送、回复、转发、整理或删除邮件，管理会话线程，绑定个人邮箱或注册新邮箱。此技能是邮件任务的统一且唯一入口，通过 qwenpawmail-mcp 编排操作，当前支持 9 个个人邮箱域名。.
cron
仅在需要未来定时执行或周期执行任务时，使用本 skill。使用 qwenpaw cron list/create/get/state/update/pause/resume/delete/run 管理任务，并始终显式传入 --agent-id。.
channel_message
Use this skill to proactively send a one-way message to a user/session/channel, usually only when the user explicitly asks to send to a channel/session or when proactive notification is needed. First query sessions with qwenpaw chats list, then push with qwenpaw channels send.
cron-task-creator
Create, manage, and run scheduled automated tasks (cron jobs) in Clacky. Use this skill whenever the user wants to create a new automated task or cron job, set up recurring automation, schedule something to run daily/weekly/hourly, view all scheduled tasks, edit an existing task prompt or cron schedule, enable or…
meeting-summarizer
Summarize a completed meeting from its transcript. Produces a structured summary with key decisions, action items, and discussion highlights. Triggered automatically when a meeting ends.