Claude Code Certification
One paper across the whole course: what an agent is and how to keep control of one, the daily craft of context, prompting and verification, then configuration with CLAUDE.md, skills, hooks and MCP, and finally scaling across sessions and CI. Sat in one two-hour sitting.
- Sitting
- 2 hours
- Questions
- 60
- Pass mark
- 70%
- Price
- ₹199$9.99
Sit this when you can do these without looking them up
This is not a certificate of attendance. It is 60 questions in 2 hours at 70% with no partial credit and one attempt, and roughly a third of the paper is foundations — the certificate is for the whole language, not the parts you enjoyed.
- Say what a hook guarantees that the same rule written in CLAUDE.md does not
- Name what loads into context at the start of a session, and what only loads on demand
- Explain why a long session with three corrections in it often does worse than a fresh one
- Choose between a skill, a subagent and a hook for a given job, and justify the choice
- Describe two ways to make Claude verify its own work while you are not watching
- Say what a checkpoint will not restore, and what you still need git for
- Explain what auto mode's classifier is looking for, and what happens when it keeps blocking
If several of those are unfamiliar, the course below is free and covers all of it. If you would rather find out than guess, there is a practice paper at the same level — ten questions, marked as you go, no account, nothing recorded.
Take the free practice paperSyllabus
Every paper is drawn to this mix, so the weights are a promise rather than a guide. The numbers are how many of the 60 questions come from each area.
- 5
Agents and the loop
What separates an agent from a chatbot, the gather-act-verify loop, the built-in tool categories, and where the human sits in the loop.
- 5
Setup and surfaces
Installing and updating, starting a session in a project, the terminal against the IDE, desktop and web surfaces, and /init and /doctor.
- 6
Permissions and control
The permission modes and what each allows, auto mode and its classifier, allowlisting, checkpoints and rewinding, and what a checkpoint cannot restore.
- 6
Context management
What occupies the context window, why performance degrades as it fills, compaction and what survives it, /context and /compact, and clearing between tasks.
- 5
Prompting
Scoping a task, pointing at sources and existing patterns, describing symptoms rather than diagnoses, file references and images, and when a vague prompt is right.
- 5
Verification
Why looks-done is the default stopping condition, giving Claude a check it can run, goals and Stop hooks, adversarial review, and asking for evidence.
- 4
Planning and correction
Plan mode and the explore-plan-code sequence, when planning is overhead, interrupting and steering, and when to abandon a session rather than correct it again.
- 5
CLAUDE.md and memory
What belongs in CLAUDE.md and what does not, why a bloated file is ignored, file locations and imports, and how auto memory differs from what you wrote.
- 6
Skills and hooks
Skill structure and on-demand loading, manual invocation, hook events and configuration, and the advisory-against-deterministic distinction between the two.
- 5
MCP and subagents
What MCP connects and what it costs in context, adding and inspecting servers, subagent context isolation, restricting a subagent's tools, and delegating investigation.
- 4
Automation and CI
Non-interactive runs and output formats, scoping tools for unattended work, fanning out across files, parallel sessions and worktrees, and review in CI.
- 4
Cost and security
What drives token spend and the levers that reduce it, the threat model including prompt injection, sandboxing, and what to keep an unattended agent away from.
Everything on this syllabus is taught free
The Claude Code Masterclass course covers the whole syllabus above across 32 lessons, with a playground in each one. Work through it first — the exam is the same material under a clock.
Open the Claude Code Masterclass courseWhat sitting it is like
The exam opens full screen with a countdown, a question at a time, and a grid showing what you have answered and what you have flagged to come back to. Nothing is submitted until you say so, or the clock reaches zero.
Every answer saves to the server as you give it. If your laptop dies at question forty, sign back in and you will find question forty exactly as you left it — with however much time was left still ticking, because the clock does not pause.
Leaving full screen or switching tabs is noted but does not end your exam. It is a record, not a trap: nobody is auto-failed for a notification stealing focus.
When it ends you get your mark, a topic-by-topic breakdown, and every question with the right answer and an explanation — whether you passed or not. Passing also produces a certificate with a link anyone can verify.