Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/walterra/claude-code-helpersnpx agentmods add commands/walterra/claude-code-helpers/curriculumWrote 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/commands/walterra/claude-code-helpers/curriculum)<a href="https://agentmods.dev/commands/walterra/claude-code-helpers/curriculum"><img src="https://agentmods.dev/badge/commands/walterra/claude-code-helpers/curriculum/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/commands/walterra/claude-code-helpers/curriculum"><img src="https://agentmods.dev/badge/commands/walterra/claude-code-helpers/curriculum.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.00000 | $0.00826 |
| Opus 5.5 | $0.00000 | $0.00330 |
| Sonnet 5.5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
curriculum 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create curriculum based on current branch
Analyse the code and docs created/modified in the current branch.
Create a comprehensive onboarding guide for a new developer to learn about the code of this branch. Use your todo tools to manage progress.
User Questions
Before creating the curriculum, ask the user:
- What is the target audience? (Junior developer, experienced developer new to the codebase, reference for someone who knows the codebase well, specific role like frontend/backend/devops)
- What should be the primary focus? (Architecture overview, specific features, testing practices, deployment, etc.)
- What level of detail is needed? (High-level overview, deep technical dive, or balanced approach)
- Are there specific technologies or concepts you want emphasized?
- What format would work best? (Step-by-step tutorial, reference guide, interactive workshop, or mixed approach)
- How much time should the curriculum take to complete? (Hours, days, weeks)
Detailed Instructions
1. Read the Code
- Analyze all files changed/added in the current branch
- Use
git diff main...HEADto see changes since branching from main - Review each modified file to understand functionality and purpose
- Identify key components, modules, and their relationships
2. Identify Tech Topics
- Extract technical concepts, frameworks, and libraries used
- Note architectural patterns and design principles
- Identify APIs, data structures, and key algorithms
- Document dependencies and external integrations
- List testing approaches and development practices
3. Create Table of Contents
- Organize topics from basic to advanced concepts
- Structure learning path logically (dependencies first)
- Group related concepts together
- Include practical examples
- Add estimated learning time for each section
4. Create Documentation for Each ToC Item
- Write clear explanations for each technical concept
- Include code examples from the actual codebase
- Provide context on why each technology/pattern was chosen
- Add troubleshooting tips and common gotchas
- Link to external resources for deeper learning
- Include hands-on exercises to reinforce learning
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 · 97 lines · 0 tokens per session scan A aa39eb9c80cc
curriculum is a command published in the GitHub repository walterra/claude-code-helpers (5 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 826 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.
Other commands, from other repositories
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-0-8
A Japanese-language command that displays the current project setup progress.
setup-m365cli.es
Lesson command — Setup de M365 CLI.
prep-role
Deep prep for a specific role's interview process. The user wants to know what to expect, how to win, and what kills candidates at their level.
start-1
A guided beginner course for product managers learning Claude Code, a coding assistant that works from the command line.