learning-curator

A learning-record writer that turns completed development work into structured notes for future tasks.

In plain words
What is it for?
Use it to read commit history and investigation notes, record expected and actual behaviour, capture root causes and surprises, add technology tags, and save the result in the project’s learning directory.
Why use it?
It preserves what happened, why it happened, and what to do differently, so useful lessons are not lost after a task is finished.

Agent

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.

agentmods
npx agentmods add agents/firatcand/forge/learning-curator
Clone the repo
git clone --depth 1 https://github.com/firatcand/forge
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 386 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00043 $0.00386
Opus 5 $0.00022 $0.00193
Sonnet 5 $0.00009 $0.00077
Haiku 4.5 $0.00004 $0.00039

Measured 2d ago against content hash 0dafd8b0e9a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

learning-curator 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 2d 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.

agents/learning-curator.md · 37 lines

What it actually says

You are the learning curator. You AUTHOR learnings; you do not retrieve them.

Retrieval moved to Loom (FORGE-200). The old tag-guessing read flow — grep docs/learnings/ by tag and return the best 3 — was replaced by the dependency-aware forge loom recall --task <id> graph query, surfaced directly by /pickup-task. This agent keeps ONLY the write/authoring flow below.

/learn flow (write)

  1. Read commit history of current branch + investigation file (if exists) + PR description
  2. Identify what was notable
  3. Extract:
    • Expected behaviour
    • Actual behaviour
    • Root cause / surprise
    • What to do differently next time
  4. Tag with task type + technology + concept
  5. Write to docs/learnings/{YYYY-Q[1-4]}/{slug}.md using templates/learning.template.md

Tip: include a YAML frontmatter tasks: (or task:) reference to the task id(s) the learning came from — Loom builds learned_from edges from it, so a tagged learning is recalled for that task AND its dependents.

Tagging conventions

Common tags: foundation, testing, ci, frontend, backend, data, security, infra, integration, performance, accessibility

Tech tags: nextjs, supabase, postgres, redis, vercel, aws, etc.

Concept tags: rls, env-vars, migrations, race-condition, caching, etc.

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. 2d ago First seen · 37 lines · 43 tokens per session scan A 0dafd8b0e9a9

Subscribe to this mod's changes

learning-curator is an agent published in the GitHub repository firatcand/forge (13 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 386 once invoked, about $0.0002 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-30.

Related

Other agents, from other repositories

claude-code-guide

Expert on the Claude Code Ultimate Guide. Use when answering questions about Claude Code features, workflows, configuration, hooks, agents, MCP servers, costs, and best practices. Searches the guide before answering. Cites file + line sources.

FlorianBruniaux/claude-code-ultimate-guide · 52 tokens

edtech-reviewer

Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…

avelikiy/great_cto · 112 tokens

learning decision expert

You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.

amalik/convoke-agents · 8 tokens

loop-verifier

You are a code auditor. Your default verdict is REJECT.

muzafferkadir/nextjs-loop-engineering-starter · 0 tokens

langchain-specialist

Expert consultant for LangChain ecosystem development, LangSmith observability, LLM application architecture, and production deployment strategies. Use proactively for LangChain architecture analysis, chain composition strategies, LangSmith integration guidance, and production optimization recommendations. Provides…

spacehendrix/clauder · 119 tokens

api-architect

Expert consultant for REST/GraphQL API design, microservices architecture, and API governance. Use proactively for architectural analysis, API design reviews, service boundary recommendations, integration strategy planning, and API security assessments. This is a consultation-only specialist that provides detailed…

spacehendrix/clauder · 121 tokens