Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bromso/metapowers/plugin install legalWrote 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/nda)<a href="https://agentmods.dev/skills/bromso/metapowers/nda"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/nda/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/nda"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/nda.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.00056 | $0.00999 |
| Opus 5.5 | $0.00022 | $0.00400 |
| Sonnet 5.5 | $0.00011 | $0.00200 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
nda 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Non-Disclosure Agreement
Generate a Non-Disclosure Agreement for "$ARGUMENTS". Produce a comprehensive NDA tailored to the parties, relationship type, and confidentiality needs.
Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.
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
Check that .metapowers/legal/<project>/00-assess.md exists. If it does not exist, stop and tell the user:
"Run an Assess skill first (e.g.
/legal:risk-assessment <project>) to generate the prerequisite assessment artifact."
Process
-
Read inputs:
- Read
.metapowers/legal/<project>/00-assess.mdfor context on parties and risk profile - Read
${CLAUDE_PLUGIN_ROOT}/shared/contract-template.mdfor standard contract provisions
- Read
-
Determine NDA type:
- Mutual (bilateral) — both parties share confidential information
- One-way (unilateral) — only one party discloses confidential information
- Identify the disclosing and receiving parties
-
Define parties:
- Full legal names and entity types
- Jurisdictions of incorporation
- Principal business addresses
- Authorized signatories
-
Draft the following sections:
- Definition of Confidential Information — broad definition with specific examples relevant to the business context (technical data, business plans, customer lists, financial information, trade secrets, product roadmaps, source code, algorithms, etc.)
- Exclusions from Confidential Information — standard exclusions:
- Information in the public domain (not through breach)
- Information independently developed without use of confidential information
- Information already known to the receiving party prior to disclosure
- Information received from a third party without restriction
- Information required to be disclosed by law or court order (with notice obligations)
- Permitted Use and Disclosure — scope of permitted use (evaluation, negotiation, specific project), permitted recipients (employees, advisors, contractors with need-to-know)
- Obligations of Receiving Party — duty of care (at least same as own confidential information, but no less than reasonable care), security measures, marking requirements, access limitations
- Term of Agreement and Survival Period — agreement duration (typically 1-3 years), survival of confidentiality obligations beyond termination (typically 2-5 years, indefinite for trade secrets)
- Return or Destruction of Information — obligation to return or certify destruction upon request or termination, exception for legally required archival copies
- Remedies — acknowledgment that breach may cause irreparable harm, right to seek injunctive relief without posting bond (where permitted), right to recover attorneys' fees
- Governing Law — choice of law, jurisdiction for disputes, venue selection
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 · 74 lines · 56 tokens per session scan A e235e1404e2b
nda is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 999 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
chief-human-resources-officer
Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical…
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…
corporate-governance
Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of authority, insurance, and business continuity. Use this to prepare board or committee materials, record a decision that needs to be minuted, set or check approval…
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.
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.