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 cabaynes/charles-claude-skills --skill takenotesgit clone --depth 1 https://github.com/cabaynes/charles-claude-skillsWrote 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/cabaynes/charles-claude-skills/takenotes)<a href="https://agentmods.dev/skills/cabaynes/charles-claude-skills/takenotes"><img src="https://agentmods.dev/badge/skills/cabaynes/charles-claude-skills/takenotes/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/cabaynes/charles-claude-skills/takenotes"><img src="https://agentmods.dev/badge/skills/cabaynes/charles-claude-skills/takenotes.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.00134 | $0.04458 |
| Opus 5 | $0.00067 | $0.02229 |
| Sonnet 5 | $0.00027 | $0.00892 |
| Haiku 4.5 | $0.00013 | $0.00446 |
Grade A, and why
takenotes 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/takenotes — Harvest a session into durable memory
Write this session's durable knowledge somewhere it survives a /clear.
This is not a transcript dump. It is a harvest, a reconcile, and a routing decision.
The value of this skill over a plain "save that to memory" is Step 3. Anyone can append a new fact. Almost nobody goes back and checks whether what's already stored is still true. Do not skip it.
Step 0 — Scope gate (always first)
Decide which of these you're doing. Getting this wrong makes the skill annoying to use.
| Situation | Do this |
|---|---|
| One discrete fact ("remember I prefer tabs", "the API key rotates monthly") | Take the single-fact path below. Do not run Steps 2–5. |
| Session checkpoint — solved a problem, made a decision, finished a feature, asked to "save what we learned" | Full harvest. Continue to Step 1. |
A topic argument was passed (/takenotes auth flow) |
Full harvest, but scope Steps 2–4 to that topic only. |
Called from /putdown |
Full harvest. Continue to Step 1. |
| Nothing durable happened (pure Q&A, reading code, no decisions) | Say so plainly in one line and stop. Do not manufacture findings to look productive. |
Single-fact path
Skipping Steps 2–5 must not mean skipping the rules for writing a memory correctly. Do all of these, then stop:
- Locate the memory directory (Step 1a) — you still need to know where to write.
- Check for an existing memory on the topic (
ls "$MEMDIR/memory/") and update it rather than adding a second file that says nearly the same thing. - Decide scope. If the fact is about how the assistant should work or who you are, it applies to every project, not just this one — see Shared memories in Step 4a. If it's about this codebase, it's local.
- Add the one-line pointer to
MEMORY.md— a memory file with no index entry is a file nothing loads. - Say what you did, including the file path and whether it applies beyond this project.
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 · 354 lines · 134 tokens per session scan A 0e9352ba4162
takenotes is a skill published in the GitHub repository cabaynes/charles-claude-skills (1 stars, last pushed yesterday), licensed MIT. It adds 134 tokens to every session and 4,458 once invoked, about $0.0007 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
distill-habits
Review recent Claude Code conversations, distill the user's stable habits and preferences, persist them into a long-term habit ledger, and maintain a "My Habits" block in the global CLAUDE.md within a character budget. The more you use Claude Code, the more it knows you. Trigger manually with /distill-habits, or on a…
dream
A read-only review of project memories, notes, instructions, documents, and selected session records that produces a detailed report and a browser-viewable HTML report. It suggests ideas and insights but does not apply changes.
shipkit-work-memory
Log session progress and save resume state. Infers from conversation and git. Triggers: 'log progress', 'session summary', 'checkpoint', 'save progress', 'end session'.
shipkit-claude-md
Update CLAUDE.md with learnings, preferences, or project context. Use when user says "update claude.md", "add to claude.md", or wants to persist something.
init-project-memory
Use when the user says "init memory", "set up memory", "scaffold memory", "init project memory", or invokes /init-project-memory — creates the .claude/ session memory system in a new project.
session-update
Use when the user says "update session", "log progress", "checkpoint session", or invokes /session-update — especially before /clear or handoff.