agentmods.dev

problem-log

problem-log is a skill for Claude Code, Codex from nataliacorrea03/claude-code-skills. It costs 69 tokens per session (479 once invoked), scanned A, original, MIT.

A daily record of the real problems you solve in Claude Code, saved as a local Markdown file. It reads your previous day's sessions and summarizes each substantial problem, approach, outcome, and tools used.

In plain words
What is it for?
Use it to prepare standups, reviews, or interviews, or to keep a personal record of technical decisions, debugging, dead ends, and solutions.
Why use it?
It removes the need to remember and write up your work manually. It leaves out routine conversation and simple lookups.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions Claude Code.

not rated 4repo 3mo ago A scan 69 tokens original MIT

Good fit Use it to prepare standups, reviews, or interviews, or to keep a personal record of technical decisions, debugging, dead ends, and solutions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nataliacorrea03/claude-code-skills/problem-log
View source ↗ nataliacorrea03/claude-code-skills
Install

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.

Any agent
npx skills add nataliacorrea03/claude-code-skills --skill problem-log
Clone the repo
git clone --depth 1 https://github.com/nataliacorrea03/claude-code-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for problem-log

README.md
[![agentmods](https://agentmods.dev/badge/skills/nataliacorrea03/claude-code-skills/problem-log/github.svg)](https://agentmods.dev/skills/nataliacorrea03/claude-code-skills/problem-log)
Your own site
<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/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.

agentmods 80×15 button for problem-log

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 479 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00069 $0.00479
Opus 5.5 $0.00028 $0.00192
Sonnet 5.5 $0.00014 $0.00096
Haiku 4.5 $0.00007 $0.00048

Measured 2mo ago against content hash 1e6d72fcd05b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (build_digest.py, daily-sweep.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/problem-log/SKILL.md · 38 lines

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)

  1. Requires the claude CLI on your PATH and Python 3.
  2. Pick where the log lives (default ~/problem-log.md).
  3. Install the daily cron: 
    cp 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.plist
    (On Linux, use the crontab line in daily-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.

Files

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.

Changes

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.

  1. 2mo ago First seen · 38 lines · 69 tokens per session scan A 1e6d72fcd05b

Subscribe to this mod's changes

problem-log is a skill published in the GitHub repository nataliacorrea03/claude-code-skills (4 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 479 once invoked, about $0.0003 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.

Claude CodeLLMProductivityagent-skillsai-agentsclaudedeveloper-tools
Related

problem-log compared with skills from other repositories

problem-log next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
problem-lognataliacorrea03/claude-code-skillsSkill43mo agoMITA69Claude Code, Codex
apple-remindersNousResearch/hermes-agentSkill262ktodayMITA17Claude Code, Codex
apple-notesNousResearch/hermes-agentSkill262ktodayMITA17Claude Code, Codex
boxNousResearch/hermes-agentSkill262ktodayMITA14Claude Code, Codex
obsidianNousResearch/hermes-agentSkill262ktodayMITA19Claude Code, Codex
channels-setupCopilotKit/CopilotKitSkill39ktodayMITA141Claude Code
mantis-configuregoogle/mantisSkill2.7k3d agoApache-2.0A77Claude Code, Codex