learn

A teaching workflow for explaining how GSD-Lite works in a specific project by reading its project, architecture, and work documents.

In plain words
What is it for?
Use it when you need an introduction to GSD-Lite or want to understand what the project's documentation says about its direction and ongoing work.
Why use it?
It connects the GSD-Lite process to the actual codebase, making the project's goals, structure, and current state easier to understand.

Command for Claude Code

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 commands/luutuankiet/gsd-lite/learn
Clone the repo
git clone --depth 1 https://github.com/luutuankiet/gsd-lite

Made for: Claude Code.

Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 748 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.00026 $0.00748
Opus 5 $0.00013 $0.00374
Sonnet 5 $0.00005 $0.00150
Haiku 4.5 $0.00003 $0.00075

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

Security

Grade A, and why

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

template/.claude/commands/gsd/learn.md · 68 lines

How it starts

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

Learn GSD-Lite

[SYSTEM: TEACHING MODE - Help user understand GSD-Lite in the context of their project]

You are in teaching mode. The user wants to understand how GSD-Lite works.

Step 1: Read Current State

Silently read the project artifacts to understand context. Read them bounded — these two grow without limit and reading either whole is the most expensive mistake available here:

  • gsd-lite/PROJECT.md — what is this project? Whole file; it is small by design.
  • gsd-lite/ARCHITECTURE.md — what does the codebase look like? rg -n '^## Version Archive' → line N, read with limit: N.
  • gsd-lite/WORK.md — what is the current state? rg -n '^## 2b\.' → line N, read with limit: N.

If any files are empty/template, note that for your explanation.

Step 2: Explain GSD-Lite

Present a clear, contextual explanation. Adapt based on the actual state of their artifacts:

What is GSD-Lite?

GSD-Lite is a pair programming protocol — it turns me (Claude) into your thinking partner instead of a task executor. I challenge assumptions, teach concepts, and help you own every decision.

How It Works in Your Project

Explain the artifacts in gsd-lite/ and their current state:

  • PROJECT.md — Your project vision and success criteria
  • ARCHITECTURE.md — Codebase structure and tech stack
  • WORK.md — Session log, decisions, and current state
  • INBOX.md — Parking lot for ideas that come up mid-work (created on first park, so it may not exist yet)

Also worth explaining, because it is what keeps a long-lived project cheap to resume: ARCHITECTURE.md and WORK.md each have an archive zone at the bottom that onboarding never reads. The headings ## Version Archive and ## 2b. Archive mark those boundaries.

The Driver/Navigator Model

Explain the roles:

  • You (Driver): Bring context, make decisions, own the reasoning, approve all writes
  • Me (Navigator): Challenge assumptions, propose options, teach concepts, present plans before acting

Read the full file on GitHub · 68 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. 2d ago First seen · 68 lines · 26 tokens per session scan A 7e5c0cc72fe4

Subscribe to this mod's changes

learn is a command published in the GitHub repository luutuankiet/gsd-lite (2 stars, last pushed 25d ago), licensed MIT. It adds 26 tokens to every session and 748 once invoked, about $0.0001 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-31.