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 rampgit 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/ramp)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/ramp"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/ramp/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/ramp"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/ramp.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.00074 | $0.02441 |
| Opus 5 | $0.00037 | $0.01221 |
| Sonnet 5 | $0.00015 | $0.00488 |
| Haiku 4.5 | $0.00007 | $0.00244 |
Grade B, and why
ramp scanned grade B with 1 finding 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 9d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
Don't lecture — check understanding. "So if a client comes in about an eviction notice but also mentions they're on a visa — what do you do?" (Answer: both issues get noted in intake; the immigration question may need a How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/legal-clinic-uk:ramp
- Check
~/.claude/plugins/config/uk-legal-plugins/legal-clinic-uk/CLAUDE.mdis set up. If placeholders: "Ask [supervisor] to run/legal-clinic-uk:cold-start-interviewfirst." - Use the walkthrough below.
- Walk through: clinic context (from handbook) → commands → practice exercises (fake intake, practice draft, research roadmap) → verification habits.
--card: generate the one-page reference card.
/legal-clinic-uk:ramp
/legal-clinic-uk:ramp --card
Ramp: Term Onboarding
Purpose
Every term, the UK law school clinic loses its entire workforce and rebuilds from scratch. New students need to learn procedures, case management, filing conventions, and practice-area basics before they are useful. Traditionally that takes weeks of reading handbooks and asking the supervisor the same questions every term.
This skill is the guided walkthrough. It reads what the supervisor uploaded during cold-start — the handbook, the filing guides, the tribunal and court rules — and teaches it interactively, with practice exercises so students try the tools in a low-stakes setting before a real client is on the line.
Audience: students. Supervisors don't run this (they run /legal-clinic-uk:cold-start-interview).
Students are not solicitors or barristers. This onboarding makes clear from the outset that students cannot give formal legal advice independently. All outputs are supervised work product. The supervising solicitor or barrister is responsible for all work that goes to a client or is filed with a court or tribunal.
Load context
~/.claude/plugins/config/uk-legal-plugins/legal-clinic-uk/CLAUDE.md → clinic profile, practice areas, jurisdiction (E&W / Scotland / NI), handbook path, supervision style, practice-area templates.
If that file is missing or still has placeholders: "The clinic hasn't been set up yet. Ask [supervising solicitor or barrister] to run /legal-clinic-uk:cold-start-interview first."
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.
- 9d ago First seen · 147 lines · 74 tokens per session scan B 09d4b3f60534
ramp 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 74 tokens to every session and 2,441 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
brand-safety-compliance
Scans outbound copy or creator-submitted content for 6 compliance red lines — medical/efficacy, exaggeration/absolute, beauty-permanence, financial/income, fake-scarcity, fake-rapport — and returns a block/warn verdict with fix suggestions. Use when the user asks to check, scan, review, or vet copy before sending, or…
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.”.