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 lexfrei/ccc --skill learngit clone --depth 1 https://github.com/lexfrei/cccWrote 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/lexfrei/ccc/learn)<a href="https://agentmods.dev/skills/lexfrei/ccc/learn"><img src="https://agentmods.dev/badge/skills/lexfrei/ccc/learn/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/lexfrei/ccc/learn"><img src="https://agentmods.dev/badge/skills/lexfrei/ccc/learn.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00718 |
| Opus 5.5 | $0.00006 | $0.00287 |
| Sonnet 5.5 | $0.00003 | $0.00144 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
learn 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 1mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze the current session and extract key takeaways worth preserving.
Classification
Separate findings into three categories:
Personal (~/CLAUDE.md):
- General patterns and approaches that work across projects
- Tool/language insights not specific to this codebase
- Workflow preferences discovered
- Errors caused by misunderstanding that were corrected during the session
Project (CLAUDE.md):
- Architecture decisions specific to this codebase
- Project-specific conventions and patterns
- Codebase quirks and gotchas
- Integration details with project's stack
- Errors and mistakes fixed during test implementation and runs
- Insights from code review if available
Memory (auto memory system):
- User preferences and feedback specific to this project (type: user, feedback)
- Project status, ongoing initiatives, deadlines (type: project)
- References to external systems: boards, channels, dashboards (type: reference)
- Gotchas and lessons learned that are personal experience, not codebase conventions
- Anything that is project-scoped but should NOT be committed to the repo
Fallback: no project CLAUDE.md
If the project has no CLAUDE.md (or user has no write access to repo):
- Everything from Project category goes to Memory instead
- Use memory types:
projectfor architecture/conventions,feedbackfor gotchas/corrections - Do NOT create CLAUDE.md without explicit user request
Process
- Read target files before proposing changes (~/CLAUDE.md, CLAUDE.md, MEMORY.md)
- Check MEMORY.md line count — if at or above 180 lines, propose cleanup of stale/outdated entries before adding new ones
- Check for duplicates or overlapping content across ALL targets — skip if already covered
- Skip findings if found in another file (e.g. project item already in ~/CLAUDE.md globally)
- Decide where each item fits best within existing structure (don't create new sections unless nothing fits)
- Formulate concisely, matching the style of existing content
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.
- 1mo ago First seen · 87 lines · 14 tokens per session scan A da20d04f94b0
learn is a skill published in the GitHub repository lexfrei/ccc (11 stars, last pushed 14d ago), licensed BSD-3-Clause. It adds 14 tokens to every session and 718 once invoked, about $0.0001 per session on Opus 5.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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.