daily-learnings

daily-learnings is a command for Claude Code from manishiitg/coding-agent-loop. It costs 0 tokens per session (563 once invoked), scanned A, original, MIT.

An end-of-day review command that reads the day's conversations and saves new, reusable facts, preferences, decisions, corrections, and procedures to memory and skills.

In plain words
What is it for?
Use it to review daily work, identify what should be remembered, and record changes to how the Crew should operate.
Why use it?
It prevents useful lessons from being buried in chat history and helps the Crew behave consistently in future conversations.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it to review daily work, identify what should be remembered, and record changes to how the Crew should operate.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/manishiitg/coding-agent-loop/daily-learnings
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.

Clone the repo
git clone --depth 1 https://github.com/manishiitg/coding-agent-loop

Made for: Claude Code.

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 daily-learnings

README.md
[![agentmods](https://agentmods.dev/badge/commands/manishiitg/coding-agent-loop/daily-learnings/github.svg)](https://agentmods.dev/commands/manishiitg/coding-agent-loop/daily-learnings)
Your own site
<a href="https://agentmods.dev/commands/manishiitg/coding-agent-loop/daily-learnings"><img src="https://agentmods.dev/badge/commands/manishiitg/coding-agent-loop/daily-learnings/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 daily-learnings

Your own site · 80×15
<a href="https://agentmods.dev/commands/manishiitg/coding-agent-loop/daily-learnings"><img src="https://agentmods.dev/badge/commands/manishiitg/coding-agent-loop/daily-learnings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 563 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.00000 $0.00563
Opus 5.5 $0.00000 $0.00225
Sonnet 5.5 $0.00000 $0.00113
Haiku 4.5 $0.00000 $0.00056

Measured 22d ago against content hash aeafb67d5cc6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

daily-learnings 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 22d 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.

agent_go/internal/workproduct/commands/daily-learnings.md · 41 lines

How it starts

The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Do this Crew's end-of-day learning review: read today's conversations, then save what is new and worth keeping into memory and skills.

{{context}}

1. Read today's conversations

  • Today's date is in the context above; if not, use the system date.
  • Read every conversation this Crew had today, not just the current chat:
    • builder/conversation/<YYYY-MM-DD>/ — chats with this Crew's owner;
    • builder/crew-chats/users/*/ — other users' chats with this Crew (use each file's modification time or message timestamps to find today's).
  • Files are JSON: conversation_history[].Role and .Parts[].Text. They can be large; skim, search (e.g. jq, grep) and focus on user requests, corrections, decisions, outcomes and repeated procedures. Skip tool output noise.
  • If a date other than today is given in the context (e.g. "yesterday" or a specific date), review that day instead.

2. Decide what is a learning

Keep only things that are new today and would change how this Crew works next time:

  • facts, preferences, decisions, constraints and corrections — test each with "Crew should remember that…";
  • procedures that worked (or failed and were fixed) and will recur — test each with "When asked to do X, Crew should…";
  • mistakes the user had to correct, with the correct approach.

Leave out transient status, one-off details, raw chat, guesses, unverified research and credentials. If nothing new qualifies, say so and change nothing.

3. Update memory

  • Read the project-root MEMORY.md first (create it if missing).
  • Follow the project memory contract: concise reverse-chronological entries, one topic per dated heading, merge into an existing topic instead of duplicating, and replace or remove entries that today's evidence contradicts.

4. Update skills

Invoking this command is my explicit ask to preserve reusable procedures:

  • Call list_skills first and read the names and descriptions of existing project skills.
  • Create or update focused project-local skills at skills/<skill-name>/SKILL.md (with name and description frontmatter) — never the account-wide skills/custom/ library. Update an existing skill only for the same topic and trigger; otherwise create a new, clearly named one; split catch-all skills.
  • Select each created or updated skill with update_project_skill_selection.

Read the full file on GitHub · 41 lines

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. 22d ago First seen · 41 lines · 0 tokens per session scan A aeafb67d5cc6

Subscribe to this mod's changes

daily-learnings is a command published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 563 tokens. 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-09-25.