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 ThomasMoreAI/legal-skills-open --skill session-bossmann007git clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/session-bossmann007)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/session-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/session-bossmann007/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/thomasmoreai/legal-skills-open/session-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/session-bossmann007.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.00088 | $0.00577 |
| Opus 5.5 | $0.00035 | $0.00231 |
| Sonnet 5.5 | $0.00018 | $0.00115 |
| Haiku 4.5 | $0.00009 | $0.00058 |
Grade A, and why
session-bossmann007 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 26d 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.
This is a copy
89% identical to session — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/session
- Parse
$ARGUMENTS— subject and N. If missing, ask:What subject, and how many questions? (e.g.,
Evidence 10orContracts 5 --essay.) - Load
~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md→ jurisdiction, exam format, weak subjects. - Load
~/.claude/plugins/config/claude-for-legal/law-student/study-plan.yamlif it exists. Readsession_historyfor this subject to weight subtopics toward where the student has been weak. - Route by method flag:
--1a-fase(default for Exame de Ordem subjects): loadbar-prep-questionsskill, run N objective questions. Apply jurisdiction handling (see that skill's## Jurisdiction handling). Label each[OAB/majority]or[area-specific].--2a-fase: loadbar-prep-questions, run N practical-professional prompts. Grade per essay-mode rubric.--flashcards: loadflashcardsskill, run N cards in--drillmode.
- Run N questions one at a time. After each, explain right/wrong and flag rule-body when jurisdictions diverge.
- At session end, write session results:
- If
study-plan.yamlexists: append tosession_historyper the schema in thestudy-planskill. - If not: write to
~/.claude/plugins/config/claude-for-legal/law-student/session-history.yaml.
- If
- Report:
- Score: X/N (percentage)
- Missed: list with subtopic tags
- Weak subtopics this session
- Pattern vs. prior sessions on this subject (if history has 2+ prior)
- What the plan now recommends next
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 26d ago First seen · 35 lines · 88 tokens per session scan A 7ab40a6ae020
session-bossmann007 is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 88 tokens to every session and 577 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to session, differing in 23 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…