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 contestacao-espelhada-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/contestacao-espelhada-bossmann007)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/contestacao-espelhada-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/contestacao-espelhada-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/contestacao-espelhada-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/contestacao-espelhada-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.00156 | $0.05144 |
| Opus 5.5 | $0.00062 | $0.02058 |
| Sonnet 5.5 | $0.00031 | $0.01029 |
| Haiku 4.5 | $0.00016 | $0.00514 |
Grade A, and why
contestacao-espelhada-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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/contestacao-espelhada
Uma contestação bem estruturada não discute; ela mapeia. Para cada alegação do autor, você diz: (a) se é fato (impugnável) ou direito (não impugnável), (b) se está impugnando, qual é a defesa (é falso, é incompleto, é irrelevante, é prescricionário, é insuficiente), (c) que prova você tem / precisa, (d) quem tem o ônus. Esta skill constrói esse mapa — o scaffold da contestação — deixando o advogado preencher com a defesa específica do seu caso.
- Load
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md→ case theory (sua versão dos fatos), side (você é réu), decision posture. - Ask the user to paste or describe the petição inicial (or key excerpts).
- Decompose: each causa de pedir, each pedido, flagging the factual vs. legal elements.
- Produce: a matrix — "alegação do autor | defesa (preliminar / mérito) | prova | ônus" — with gaps and open questions marked for the attorney to fill in.
Contestação Espelhada — Strategy Map
Matter context
Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (default for in-house), skip — skills use practice-level context and the matter machine 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 — especially your case theory (sua versão dos fatos), your side (você é réu), the jurisdiction, and the phase. Write outputs to the matter folder if active; otherwise to the practice-level contestacoes/ folder.
Purpose
A contestação (answer) is a structural document. It admits or denies each factual allegation (CPC art. 341 [verified: https://www.planalto.gov.br/ccivil_03/_ato2015-2018/2015/lei/l13105.htm]), then either rests (no defense on the merits) or mounts affirmative defenses (preliminares or mérito). The structure matters because:
- Failing to deny a factual allegation = admission. Art. 341 says "fato não impugnado presume-se verdadeiro" — if the author alleges "réu received the shipment on Jan. 1" and you don't deny it, the court presumes it's true. You can't later say "actually, we got it on Jan. 15" without opening yourself to a charge of surprise / lack of candor.
- Preliminary defenses stop the case before merits (CPC art. 337). If the author sued in the wrong forum, or there's res judicata, or the statute of limitations has run, you raise that first — it may end the case without a trial on the facts.
- Affirmative defenses shift the burden. Once you raise them (estoppel, laches, force majeure, release, accord and satisfaction, comparative negligence), the author has to rebut or concede. The judge doesn't award them to you automatically; you have to plead and prove them. But if you don't plead them, they're waived.
- Ônus allocation is non-trivial. Some defenses are on the defendant (most affirmative defenses — you have to prove comparative negligence, for example). Some shift to the plaintiff after you raise them (prescription is often on the defendant, but the plaintiff can affirmatively prove the obligation is still alive; depende). The matrix makes ônus explicit.
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 a32ceaf77de4
- 26d ago First seen · 252 lines · 156 tokens per session scan A 8ce983aa347a
contestacao-espelhada-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 156 tokens to every session and 5,144 once invoked, about $0.0006 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…