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 bromso/metapowers --skill legal-glossarygit clone --depth 1 https://github.com/bromso/metapowersWrote 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/bromso/metapowers/legal-glossary)<a href="https://agentmods.dev/skills/bromso/metapowers/legal-glossary"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/legal-glossary/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/bromso/metapowers/legal-glossary"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/legal-glossary.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.00061 | $0.00823 |
| Opus 5.5 | $0.00024 | $0.00329 |
| Sonnet 5.5 | $0.00012 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
legal-glossary 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 3d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legal Glossary
Generate a glossary of legal terms for "$ARGUMENTS". Define terms in plain language, organized by legal area, with practical examples and context for non-lawyers.
Note: AI-generated legal content does not constitute legal advice. Definitions are simplified for accessibility and may not capture every legal nuance.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/legal/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.
Prerequisites
None — this is a utility skill.
Process
-
Determine scope:
- Parse "" to identify which legal area(s) or terms to cover
- If a broad topic is requested, cover terms across all relevant legal areas
- If a specific area is requested, provide deeper coverage of that area
-
Organize terms by legal area:
- Contract Law — offer, acceptance, consideration, breach, damages, indemnification, force majeure, assignment, waiver, severability
- Privacy and Data Protection — personal data, data controller, data processor, consent, data subject rights, breach notification, cross-border transfer, data minimization
- Intellectual Property — copyright, trademark, patent, trade secret, licensing, fair use, infringement, prior art, work for hire
- Employment Law — at-will employment, wrongful termination, non-compete, non-solicitation, independent contractor, misclassification, FLSA, harassment, accommodation
- Compliance and Regulatory — due diligence, fiduciary duty, regulatory filing, audit, whistleblower, sanctions, anti-corruption, know your customer (KYC)
- Corporate Law — incorporation, bylaws, fiduciary duty, shareholder, board resolution, articles of incorporation, operating agreement, capitalization, vesting
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.
- 3d ago First seen · 54 lines · 61 tokens per session scan A fbeeb02bc5a9
legal-glossary is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 823 once invoked, about $0.0002 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-21.
Other skills, from other repositories
tax
Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check…
contract-review
Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, proposing positions, and recommending a path rather than listing issues. Use this to review a contract before signature, prepare a negotiation position, build fallback…
performance-management
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
examples
Provide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes, best-practice advice, or audits.