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 uk-agents/uk-legal-plugins --skill study-plangit clone --depth 1 https://github.com/uk-agents/uk-legal-pluginsWrote 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/uk-agents/uk-legal-plugins/study-plan)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/study-plan"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/study-plan/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/uk-agents/uk-legal-plugins/study-plan"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/study-plan.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.00076 | $0.03316 |
| Opus 5 | $0.00038 | $0.01658 |
| Sonnet 5 | $0.00015 | $0.00663 |
| Haiku 4.5 | $0.00008 | $0.00332 |
Grade A, and why
study-plan 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 6d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/law-student-uk:study-plan
- Load
~/.claude/plugins/config/uk-legal-plugins/law-student-uk/CLAUDE.md→ qualification route, exam format, exam date, weak subjects, target study hours/day, prep course. - Load
~/.claude/plugins/config/uk-legal-plugins/law-student-uk/study-plan.yamlif it exists. - Apply the framework below.
- Route by flag:
--build(default if no plan exists): walk the inputs gate (exam, subjects, hours/week, days off, methods). Build the phase structure + daily schedule for the first two weeks. Writestudy-plan.yaml.--update(default if plan exists): re-readsession_history, adjust subject priorities and weekly_hours, fill in the next stretch of daily schedule.--status: what's scheduled today / this week, score trend, subjects slipping, next scheduled session per subject.--cram: force cram mode — 80/20 high-yield prioritisation, daily MCQ volume, taper last 2-3 days.
- Before writing: summarise the plan in prose and confirm with the student. Adjust based on their answer.
- Always sanity-check hours/week against the student's stated life constraints. Over-ambitious plans fail.
Purpose
Sitting down to revise and not knowing what to revise is how weeks disappear. This skill builds a plan — weeks to exam, sessions per day, subjects per week, session types — and then adapts as the student actually does the sessions. It is a living plan, not a calendar export.
It also gives downstream skills (bar-prep-questions, flashcards, drill, irac-practice) a shared schedule to honour, so the student isn't asked "what do you want to study today" every time they open a session.
Confidence discipline
A plan is opinion, not doctrine. The skill states clearly what's an estimate:
- Time-per-topic estimates are general guidance (based on typical SQE prep course weightings from BPP, BARBRI UK, Kaplan, ULaw). Flag them as estimates — the student's real pace will differ.
- Subject weightings are derived from the student's own reported weak subjects and session history. Confident.
- High-yield-topic prioritisation in cram mode is based on SRA's published SQE1 assessment weightings and historical patterns from published SQE materials. Flag any "this is definitely on the exam" claim as
[UNCERTAIN — past frequency is not a prediction].
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.
- 6d ago First seen · 235 lines · 76 tokens per session scan A 19abc72ff66e
study-plan is a skill published in the GitHub repository uk-agents/uk-legal-plugins (9 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 3,316 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
ask
Answer a question from a finished study, citing back into its evidence, and say plainly when the study does not cover it.
compare
Set two term tables against each other — same concept different term, same term different concept, and what each covers that the other lacks.
enablement-course
Assemble an internal AI enablement course for a company's own employees, sized to where they actually are rather than where a vendor deck assumes they are. Produces the session plan, per-session content and exercises, a facilitator guide for a non-expert, and a way to tell whether it worked. Builds on the tech stack…
study-deps
Use when pulling upstream source or cloning a dependency at its installed version to study internals, read code, or create pinned worktrees.
brief
Use when confusion is only “huh,” “wait, what,” “sorry, you lost me,” or “slow down; explain simply and keep it short.”.
postgres
Use this skill for any PostgreSQL database work — table design, indexing, data types, constraints, extensions (pgvector, PostGIS, TimescaleDB), search, and migrations. Trigger when user asks to: Design or modify PostgreSQL tables, schemas, or data models Choose data types, constraints, indexes, or partitioning…