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 nataliacorrea03/claude-code-skills --skill problem-loggit clone --depth 1 https://github.com/nataliacorrea03/claude-code-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/nataliacorrea03/claude-code-skills/problem-log)<a href="https://agentmods.dev/skills/nataliacorrea03/claude-code-skills/problem-log"><img src="https://agentmods.dev/badge/skills/nataliacorrea03/claude-code-skills/problem-log.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.1 | $0.00069 | $0.00479 |
| Opus 5 | $0.00034 | $0.00239 |
| Sonnet 5 | $0.00014 | $0.00096 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
problem-log 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 7d 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.
What it actually says
problem-log
You solve real problems in Claude Code every day and forget them by next week. This logs them automatically.
Once a day a cron reads that day's Claude Code sessions, finds the genuine problem-solving arcs (a bug you chased down, a design decision with tradeoffs, a diagnosis that overturned your first guess), and appends a short entry for each to a markdown file. No manual step. Routine chatter and simple lookups are skipped.
What you get, per arc
- Problem — the friction in one line
- Approach & iteration — how you worked it, including dead ends and pivots
- Outcome — what actually resolved it
- Tools — what you used
- Date + source session id
Setup (2 minutes)
- Requires the
claudeCLI on your PATH and Python 3. - Pick where the log lives (default
~/problem-log.md). - Install the daily cron:
(On Linux, use thecp com.example.problem-log-daily.plist ~/Library/LaunchAgents/ # edit the path inside to point at this folder, then: launchctl load ~/Library/LaunchAgents/com.example.problem-log-daily.plistcrontabline indaily-sweep.sh's header instead.)
Run it by hand
./daily-sweep.sh # log yesterday's arcs now
./daily-sweep.sh dry # print what it would log, write nothing
How it works
build_digest.py (pure local, no LLM) reads your session transcripts from ~/.claude/projects, keeps only the human/assistant text, and drops trivial sessions. Then a headless claude pass reads that digest per SWEEP_PROMPT.md and appends the arcs to your log file. Nothing leaves your machine except the model call you already use.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 38 lines · 69 tokens per session scan A 1e6d72fcd05b
problem-log is a skill published in the GitHub repository nataliacorrea03/claude-code-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 479 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
notebooklm-manager
Manages NotebookLM notebooks — query, add, list, search, enable/disable, remove. Use when a notebooklm.google.com URL appears or user mentions NotebookLM. Handles URLs through its own Chrome agent — do not navigate directly. Requires: claude-in-chrome MCP.
lx
Codebase exploration tool that reads many files or whole directories in a single call, with per-file headers, glob include/exclude filters, function/type skeleton extraction (signatures only, no bodies), and head/tail line slicing.
morning-triage
Discovery for an autonomous loop — find this turn's work instead of being handed it. Reads what changed since the last run (failed CI, new issues, merged commits), judges what's actually worth acting on, writes findings to a durable state file, and hands each off to the SDLC loop with a stop-condition. Use as the…
eco-max
Maximum-savings variant of /eco - the same frugality rules PLUS a low reasoning-effort override for the invoked task. Use for routine chores (rename, small fix, quick question, boilerplate) when the user wants absolute minimum token spend; prefer plain /eco for hard or high-stakes work. Works in any language.
keel-handover
Add this session's block to HANDOVER.md before ending or compacting — done / tried-failed / latest / next. Rotates via /keel-distill when the 3-block cap is hit.
ops-client
Use when directly operating or verifying a specified real desktop client, or gathering evidence for an isolated client-layer failure; require a verified target, window, and capability, not browser-page verification, source changes, or cross-system diagnosis.