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 tese-vinculante-checker-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/tese-vinculante-checker-bossmann007)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/tese-vinculante-checker-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/tese-vinculante-checker-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/tese-vinculante-checker-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/tese-vinculante-checker-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.00227 | $0.02907 |
| Opus 5.5 | $0.00091 | $0.01163 |
| Sonnet 5.5 | $0.00045 | $0.00581 |
| Haiku 4.5 | $0.00023 | $0.00291 |
Grade A, and why
tese-vinculante-checker-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 24d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tese-vinculante-checker
- Load
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md→ role, decision posture, jurisdiction. - If matter workspaces enabled, confirm or select the active matter; load
matter.md. - Interview the user to capture thesis description, side, jurisdiction, phase.
- Structure binding-authority research protocol.
- Produce checklist; guide user through search sources.
- Interpret results user pastes back.
- Output per thesis: binding authority status, sobrestamento risk, recommendation.
Tese Vinculante — Verificação Pré-Protocolo
Matter context
Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /litigation-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md — pleaded claims, side, jurisdiction, applicable theory. Write outputs to the matter's case-analysis/ folder if a matter is active; otherwise the practice-level case-analysis/ folder.
Purpose
A central legal thesis lives or dies on whether a superior court has already ruled against it, or is about to hold it against you nationally while your case is pending. This skill surfaces binding and persuasive authority before filing. Filing into a súmula vinculante that contradicts your thesis, or into an active IRDR on the identical issue, or while a tema de repercussão geral is pending before the STF, means the case is dead — or will be suspended while the higher court rules — before service.
Jurisdiction assumption / Premissa de jurisdição (Brasil)
Brazilian appellate authority comes in binding (vinculante) and persuasive (persuasiva) tiers:
Binding:
- Súmula Vinculante STF (Lei 11.417/2006 [verified: https://www.planalto.gov.br/ccivil_03/_ato2004-2006/2006/lei/l11417.htm]) — applicable to lower courts and public administration under the binding-effect framework. A lower court contradicting it is reversible on appeal.
- Temas de Repercussão Geral (STF) (CF/88 art. 102, §3º; CPC art. 1.035
[verified: https://www.planalto.gov.br/ccivil_03/constituicao/constituicao.htm; https://www.planalto.gov.br/ccivil_03/_ato2015-2018/2015/lei/l13105.htm]) — when STF declares constitutional/statutory question has general repercussion, cases pending on that identical theme are typically suspended (sobrestamento) under CPC art. 1.037 [verified: https://www.planalto.gov.br/ccivil_03/_ato2015-2018/2015/lei/l13105.htm] until STF rules. - Recursos Repetitivos (STJ) (CPC arts. 1.036-1.041 [verified: https://www.planalto.gov.br/ccivil_03/_ato2015-2018/2015/lei/l13105.htm]) — when STJ marks a recurring question as "repetitive appeal," lower-court decisions are suspended pending STJ's ruling on the thesis, then applied uniformly.
- IRDR (CPC arts. 976-987 [verified: https://www.planalto.gov.br/ccivil_03/_ato2015-2018/2015/lei/l13105.htm]) — state (TJ) or federal (TRF) consolidation of identical theses; binds all cases in that court system on the question. Suspends pending cases while IRDR is resolved.
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.
- 24d ago Changed 8d4dbc1da884
- 26d ago First seen · 189 lines · 227 tokens per session scan A e393468f4f20
tese-vinculante-checker-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 227 tokens to every session and 2,907 once invoked, about $0.0009 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-10-02.
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…