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/umputun/cc-thingz/learnnpx skills add umputun/cc-thingz --skill learngit clone --depth 1 https://github.com/umputun/cc-thingzWrote 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/umputun/cc-thingz/learn)<a href="https://agentmods.dev/skills/umputun/cc-thingz/learn"><img src="https://agentmods.dev/badge/skills/umputun/cc-thingz/learn.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.00094 | $0.01803 |
| Opus 5 | $0.00047 | $0.00901 |
| Sonnet 5 | $0.00019 | $0.00361 |
| Haiku 4.5 | $0.00009 | $0.00180 |
Grade C, and why
learn scanned grade C with 1 finding 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
**Counter-example:** *"We keep credentials in `~/.aws/credentials`"* mentions a user-home path but describes a team-wide convention — the path is illustrative, not per-developer state. Such notes belong in project CLAUDE How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learn
Review the current conversation history and identify strategic, reusable project knowledge that should be captured in the project CLAUDE.md file. When the project has opted into Claude Code's three-tier memory convention by creating CLAUDE.local.md, route genuinely personal or environment-specific discoveries there instead.
Analysis Process
-
Review Session History
- Examine all files read and modified during this session
- Identify patterns discovered while working on tasks
- Note architectural insights gained from exploring the codebase
-
Extract Strategic Knowledge
- Filter out tactical details (bug fixes, specific implementations)
- Focus on reusable patterns and project structure
- Identify conventions and architectural decisions
-
Categorize Findings
- Project architecture and structure
- Data flow patterns
- External service integrations
- Project-specific conventions
- Key dependencies and their purposes
- Configuration patterns
- Testing strategies
- Build and deployment processes
- Operational knowledge (debugging, DevOps)
Destinations
This skill writes to one of two files in the project root:
-
CLAUDE.md(project memory, committed, team-shared) — the default destination. Use for architecture, conventions, integration patterns, and any other knowledge useful to the whole team. -
CLAUDE.local.md(local memory, gitignored personal overrides) — used only when both conditions hold:CLAUDE.local.mdalready exists in the project (the project has opted into the three-tier memory convention).- The discovery describes per-developer / per-checkout state — not just mentions something personal, but the knowledge itself is meaningful only to the current developer on this machine. Examples: a tool-loading workaround that depends on this developer's interpreter / runtime setup, a personal alias, a per-checkout env override.
Counter-example: "We keep credentials in
~/.aws/credentials" mentions a user-home path but describes a team-wide convention — the path is illustrative, not per-developer state. Such notes belong in project CLAUDE.md. When in doubt about whether a discovery is genuinely personal, default to project CLAUDE.md.
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 · 159 lines · 94 tokens per session scan C 123f98b43061
learn is a skill published in the GitHub repository umputun/cc-thingz (466 stars, last pushed 11d ago), licensed MIT. It adds 94 tokens to every session and 1,803 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
plugin
Manage Claude Code plugins — add marketplaces, install, update, remove, list. Use when installing plugins, checking status, or managing the registry.
flow-next-interview
In-depth Q&A to refine a spec, task, or spec file before building. Use when asked to flesh out, refine, or interrogate requirements.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-spec-completion-review
Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.
flow-next-guide
Recommend the smallest sufficient flow-next workflow from the starting state. Stateless router. Use when unsure which command or stage applies next.
flow-next-land
Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.