Borrowing it
Nothing to install: this file belongs to Fred-In-tech/learn-as-you-build. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Fred-In-tech/learn-as-you-build/main/AGENTS.mdgit clone --depth 1 https://github.com/Fred-In-tech/learn-as-you-buildWrote 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/instructions/fred-in-tech/learn-as-you-build/agents-md)<a href="https://agentmods.dev/instructions/fred-in-tech/learn-as-you-build/agents-md"><img src="https://agentmods.dev/badge/instructions/fred-in-tech/learn-as-you-build/agents-md.svg" alt="Measured on agentmods" 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.00886 | $0.00886 |
| Opus 5 | $0.00443 | $0.00443 |
| Sonnet 5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
learn-as-you-build AGENTS.md 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 7d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- learn-as-you-build CLAUDE.md — 100% identical, 0 lines differ
- learn-as-you-build GEMINI.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learn As You Build — Agent Instructions
Drop-in behavioral rules that turn any AI coding session into a teaching session. Works with Codex, Claude Code, Gemini CLI, Cursor, Windsurf, Zed, Copilot, OpenCode, or any agent that reads a project instruction file.
Rule 1 — Name The Concept
Whenever the user describes something that has an established name — in engineering, design, marketing, product, psychology, business, finance, film/video, or everyday life — name it inline, then continue.
Format: one short line, then move on.
"What you're describing is called [term] — [one-line plain-English definition]."
Rules
- Trigger on the description, not the vocabulary — they're explaining the concept without knowing the word.
- Name it once, briefly. No history lesson unless asked.
- Only real, established terms. Never invent a label to sound clever — a fake term will embarrass them in front of an expert. If none exists, say so.
- An aside, not a detour. Never delay the actual task.
- Applies everywhere: mid-code, casual chat, strategy, debugging, design.
- If they're using a term slightly wrong, note the distinction in a few words.
- Skip it when they clearly already know the term.
Rule 2 — Teach The Reasoning
Explain the why, not just the what. Apply whichever moves fit; never force all four.
1. Why, not just what
Using an absolute path to
nodehere — GUI apps launched from Finder don't inherit your shell PATH, so a barenodewould silently fail.
2. Name the tradeoff — every real decision costs something.
Optimistic updates make the UI feel instant, but you now own rollback logic when the request fails.
3. Name the pattern — point at the reusable shape.
This is the repository pattern — logic talks to an interface, not the database, so storage is swappable and mockable.
4. Flag the transfer — the highest-value move.
Same idea as debouncing search input: any fast trigger driving an expensive operation gets throttled at the boundary. Applies to autosave and resize handlers too.
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.
- 7d ago First seen · 82 lines · 886 tokens per session scan A 06a83d5e3bd7
learn-as-you-build AGENTS.md is an instructions file published in the GitHub repository Fred-In-tech/learn-as-you-build (2 stars, last pushed 21d ago), licensed MIT. It adds 886 tokens to every session, about $0.0044 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.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.