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 marketing-claims-review-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/marketing-claims-review-bossmann007)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/marketing-claims-review-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/marketing-claims-review-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/marketing-claims-review-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/marketing-claims-review-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.00072 | $0.03365 |
| Opus 5.5 | $0.00029 | $0.01346 |
| Sonnet 5.5 | $0.00014 | $0.00673 |
| Haiku 4.5 | $0.00007 | $0.00336 |
Grade A, and why
marketing-claims-review-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 12d 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 marketing-claims-review — 34 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.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/marketing-claims-review
- Load
~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md→ Marketing claims standards. - Apply the claim taxonomy and review workflow below.
- Extract every claim. Classify: puffery / factual / comparative / implied / absolute.
- For each non-puffery claim: substantiation check, suggested fix.
- Output: claim-by-claim with calls, suggested revision if short enough.
/product-legal:marketing-claims-review
[paste landing page copy]
Matter context
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 /product-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/product-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Purpose
Marketing wants to say the product is the best. Legal needs it to be true, or at least not provably false. This skill finds the claims that will get a demand letter from a competitor or an inquiry from a regulator, and suggests how to keep the energy while fixing the exposure.
Load standards
Read ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md → ## Marketing claims:
- Comparative claims policy (allowed with substantiation / discouraged / never)
- Substantiation standard (what's required before a claim ships)
- Common rejected claims (learn from history)
Research the applicable standards before clearing copy
Research the currently operative advertising and substantiation standards for the applicable jurisdictions and media (for example, CDC — Código de Defesa do Consumidor, Lei 8.078/1990 — arts. 30-38 on publicidade enganosa e abusiva and oferta, CONAR and its Código Brasileiro de Autorregulamentação Publicitária, SENACON guidance, sector regulators for healthcare / financial / children's products, and platform-specific policies). Identify what substantiation the specific claim requires — who measured it, when, sample size, apples-to-apples basis — not just whether some substantiation exists on file. Flag implied claims and comparative claims for heightened scrutiny. Verify currency: CONAR representations, SENACON notas técnicas, and disclosure rules are updated and continue to evolve. Cite primary sources with pinpoint references. If you cannot verify the current standard, flag for attorney verification — do not state a rule you haven't confirmed.
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.
- 12d ago Changed b4145fb85e21
- 14d ago First seen · 225 lines · 72 tokens per session scan A d846c5073b15
marketing-claims-review-bossmann007 is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (88 stars, last pushed 3d ago), licensed Apache-2.0. It adds 72 tokens to every session and 3,365 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to marketing-claims-review, differing in 34 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…