learning

A memory agent that records how you work, including your tool choices, corrections, coding preferences, and past outcomes. It stores these observations so they can guide later coding sessions.

In plain words
What is it for?
Use it to remember choices such as testing frameworks, commit conventions, preferred coding patterns, and which recommendations or generated changes you previously adjusted.
Why use it?
It reduces the need to repeat preferences and corrections every time you start work. It helps the other agents make choices that better match your established way of working.

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/nxtg-ai/forge-plugin/learning
Clone the repo
git clone --depth 1 https://github.com/nxtg-ai/forge-plugin
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 1,337 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.00000 $0.01337
Opus 5 $0.00000 $0.00668
Sonnet 5 $0.00000 $0.00267
Haiku 4.5 $0.00000 $0.00134

Measured yesterday against content hash a93d11df37e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

learning 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 yesterday.

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.

docs/agents/learning.md · 116 lines

How it starts

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

Learning

The adaptive memory that makes NXTG-Forge smarter every session -- capturing your preferences, patterns, and corrections so the system stops guessing and starts knowing.

Level L1 Vibe Coder
Category Governance & Analysis
Model Haiku

What It Does

The Learning agent is NXTG-Forge's institutional memory. It observes how you work -- which agents you invoke, what corrections you make, what coding patterns you prefer -- and encodes those observations into persistent preferences that improve every future session.

Without this agent, every session starts from zero. You would repeat the same corrections ("I use Vitest, not Jest"), re-explain the same preferences ("conventional commits, always"), and watch the system make the same wrong guesses. The Learning agent eliminates that repetition by capturing signals from your behavior and making them available to all other agents.

It draws from three signal sources: session history (which agents run, in what order, how often), user corrections (when you override a recommendation or modify generated code significantly), and outcome tracking (did the generated code pass tests, was the commit accepted). The strongest signal is always an explicit correction -- when you say "I prefer X over Y," that preference is treated as authoritative.

When to Use It

  • Repeated corrections: When you find yourself telling the system the same thing across multiple sessions -- "I use pnpm, not npm" or "I always want TypeScript strict mode."
  • Recommendation quality is poor: When agent suggestions consistently miss the mark and you want the system to learn from your actual workflow patterns.
  • Preference capture: When you want to explicitly set preferences for testing frameworks, commit styles, file organization, or code formatting that should persist.
  • Pattern audit: When you want to understand what the system has learned about your workflow and verify it matches your actual preferences.

Read the full file on GitHub · 116 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. yesterday First seen · 116 lines · 0 tokens per session scan A a93d11df37e0

Subscribe to this mod's changes

learning is an agent published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,337 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-08-31.