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.
git clone --depth 1 https://github.com/firatcand/forgeWrote 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/agents/firatcand/forge/learning-curator)<a href="https://agentmods.dev/agents/firatcand/forge/learning-curator"><img src="https://agentmods.dev/badge/agents/firatcand/forge/learning-curator/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.
<a href="https://agentmods.dev/agents/firatcand/forge/learning-curator"><img src="https://agentmods.dev/badge/agents/firatcand/forge/learning-curator.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.00386 |
| Opus 5.5 | $0.00017 | $0.00154 |
| Sonnet 5.5 | $0.00009 | $0.00077 |
| Haiku 4.5 | $0.00004 | $0.00039 |
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 1mo 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
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-awareforge loom recall --task <id>graph query, surfaced directly by/pickup-task. This agent keeps ONLY the write/authoring flow below.
/learn flow (write)
- Read commit history of current branch + investigation file (if exists) + PR description
- Identify what was notable
- Extract:
- Expected behaviour
- Actual behaviour
- Root cause / surprise
- What to do differently next time
- Tag with task type + technology + concept
- Write to
docs/learnings/{YYYY-Q[1-4]}/{slug}.mdusingtemplates/learning.template.md
Tip: include a YAML frontmatter
tasks:(ortask:) reference to the task id(s) the learning came from — Loom buildslearned_fromedges 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.
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.
- 1mo ago First seen · 37 lines · 43 tokens per session scan A 0dafd8b0e9a9
learning-curator is an agent published in the GitHub repository firatcand/forge (13 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 386 once invoked, about $0.0002 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-30.
Other agents, from other repositories
gsd-mempalace-curator
Ship-time MemPalace curation — writes the session diary, proposes/creates cross-project tunnels, mirrors extract-learnings into the temporal KG, and runs wing-scoped drawer pruning. Spawned at ship:post by the mempalace capability.
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…
knowledge-extractor
Deep-analysis agent spawned by /crystallize. Reads session logs and lessons.md, clusters patterns with ≥3 occurrences, and writes draft skill files to skills/{domain}/SKILL.md.
data-engineer
Expert consultant for data pipeline design, ETL/ELT processes, data architecture, and data quality, providing analysis and recommendations without writing code. Use proactively for data infrastructure consultation, pipeline architecture guidance, stream processing strategy, data storage optimization, and data…
observability-engineer
Expert consultant for monitoring, logging, distributed tracing, and alerting for backend systems, providing analysis and recommendations without writing code. Use proactively for observability architecture design, monitoring strategy assessment, logging framework recommendations, tracing implementation guidance, and…
typescript-specialist
Expert consultant for TypeScript integration, type safety, and migration strategies, providing analysis and recommendations without writing code. Use proactively for TypeScript configuration analysis, type safety assessment, JavaScript-to-TypeScript migration planning, and framework TypeScript integration consulting.…