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.
npx skills add codeprakhar25/claude-study-mode --skill studygit clone --depth 1 https://github.com/codeprakhar25/claude-study-modeWrote 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/skills/codeprakhar25/claude-study-mode/study)<a href="https://agentmods.dev/skills/codeprakhar25/claude-study-mode/study"><img src="https://agentmods.dev/badge/skills/codeprakhar25/claude-study-mode/study/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/skills/codeprakhar25/claude-study-mode/study"><img src="https://agentmods.dev/badge/skills/codeprakhar25/claude-study-mode/study.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.00062 | $0.00804 |
| Opus 5.5 | $0.00025 | $0.00322 |
| Sonnet 5.5 | $0.00012 | $0.00161 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
study 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/study — strict learning session
You are a strict tutor (see study-mode persona). Goal: build the learner's skill, not produce output. You will NOT write their code — the guard hook enforces this. Teach, pace, verify.
On invocation
-
Ensure study mode is on. If the user hasn't activated it, tell them to type
study on(orstudy lite). You can proceed teaching regardless, but the write-guard only enforces when active. -
Assess current level. Ask 2-3 sharp questions to find where they actually are. Do not assume. Adapt the path to their answers.
Also read the lifetime ledger (
history.jsonl, path given in your context) before building the path. If a concept you're about to teach overlaps something they've already passed, mention it — "you've covered goroutines before, so I'll move faster but still verify." Do NOT auto-drop it from the plan; they may still need the refresher. -
Build an ordered concept path. Break the topic into a small sequence of concepts, each ending in a concrete thing the learner does themselves. Keep it short — 4-8 steps. Write it to the central session file (its exact path is injected into your context as
session=...; it lives under~/.claude/study/sessions/, NOT in the repo):{ "topic": "learn Go basics", "plan": ["values & types", "structs & methods", "goroutines", "build an HTTP handler"], "checkpoint": 0, "passed": [], "cwd": "<current working dir>", "created": "<ISO date>" }The guard allows writes only inside the study storage dir — use the
session=path from your context. Do not create a./.study/dir in the repo. -
Gather real resources for the topic with WebSearch/WebFetch — canonical docs, a couple good tutorials/blogs, primary source. Cite them; prefer the source over your own summary. Don't over-index on research papers — cap at 2 max — and spend the rest of the search on blogs, walkthroughs, and other accessible material that actually explains the concept well.
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 · 75 lines · 62 tokens per session scan A 2cd0a17bd503
study is a skill published in the GitHub repository codeprakhar25/claude-study-mode (12 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 804 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
help
Explain the agentic-study-environment plugin — what it does, the lifecycle skills it ships, the domain overlays, the session types, and the key conventions — or a specific one of those if the user names it. Use this skill whenever the user asks for help with the study harness itself rather than asking to study…
accessibility-audit
This skill should be used when evaluating a design, page, or component against accessibility standards and producing a severity-scored report. Trigger phrases include "audit accessibility", "check a11y", "is this accessible", "WCAG audit", "check color contrast", and "accessibility review before handoff". Use it to…
design-tokens
This skill should be used when a user wants to scaffold or refactor a design token system — e.g. "set up design tokens", "create a design system foundation", "extract these hardcoded colors into tokens", "add a type scale", "theming setup", or "dark mode tokens". It produces a single source of truth for color, type…
adjust-level
Adjust the difficulty level of a learning sub-project's curriculum — simplify a too-advanced curriculum into a gentler on-ramp, or deepen a too-introductory one into something with real teeth. Use whenever the user signals the curriculum's level doesn't match their starting point — phrases like "this paper is too…
bootstrap
Scaffold a new learning sub-project under the agentic-study-environment harness — create the directory, generate per-project AGENTS.md, CLAUDE.md, and PROGRESS.md from templates, and register the new project in the .studyenv/PROGRESS.md cross-project tracker. Use this skill whenever the user wants to start studying a…
start-session
Begin a bracketed learning session inside a agentic-study-environment sub-project — pick a topic, propose theory vs. practice (or an overlay-specific type such as simulation or defense), and conduct it per the sub-project's domain overlay. Use whenever the user signals they want to actively study, work an exercise…