vendor-agreement

vendor-agreement is a skill for Claude Code from bromso/metapowers. It costs 67 tokens per session (1,139 once invoked), scanned A, original, MIT.

A legal contract drafting skill for creating a services agreement between a buyer and an outside vendor or supplier.

In plain words
What is it for?
Use it to draft vendor agreements covering statements of work, service levels, changes, insurance, indemnities, termination, and transition.
Why use it?
It gathers important business terms in one agreement, including work scope, service standards, pricing, data protection, risk allocation, and ending the relationship. The generated text is not legal advice.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the legal plugin — 35 skills shipped together

Good fit Use it to draft vendor agreements covering statements of work, service levels, changes, insurance, indemnities, termination, and transition.

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add bromso/metapowers
Claude Code
/plugin install legal

Made for: Claude Code.

Or install legal, the plugin that ships this one along with the rest of its 35 skills.

Wrote 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.

agentmods badge for vendor-agreement

README.md
[![agentmods](https://agentmods.dev/badge/skills/bromso/metapowers/vendor-agreement/github.svg)](https://agentmods.dev/skills/bromso/metapowers/vendor-agreement)
Your own site
<a href="https://agentmods.dev/skills/bromso/metapowers/vendor-agreement"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/vendor-agreement/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.

agentmods 80×15 button for vendor-agreement

Your own site · 80×15
<a href="https://agentmods.dev/skills/bromso/metapowers/vendor-agreement"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/vendor-agreement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,139 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.01139
Opus 5.5 $0.00027 $0.00456
Sonnet 5.5 $0.00013 $0.00228
Haiku 4.5 $0.00007 $0.00114

Measured 3d ago against content hash 20ed7017e125, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vendor-agreement 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.

plugins/legal/skills/vendor-agreement/SKILL.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vendor Agreement

Draft a vendor or supplier services agreement for "$ARGUMENTS". Generate a comprehensive agreement covering scope of services, performance standards, data protection, and risk allocation.

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

  1. Read inputs:

    • Read .metapowers/legal/<project>/00-assess.md for risk and jurisdiction context
    • Read ${CLAUDE_PLUGIN_ROOT}/shared/contract-template.md for standard contract provisions
  2. Identify engagement context:

    • Nature of services being procured
    • Vendor type (technology, consulting, staffing, facilities, etc.)
    • Engagement duration and renewal expectations
    • Data access and sensitivity level
    • Criticality to business operations
  3. Draft the following sections:

    • Scope of Services — detailed description of services with reference to Statement of Work (SOW), deliverables and acceptance criteria, out-of-scope items explicitly excluded
    • Performance Standards and SLAs — measurable performance metrics, reporting frequency and format, remedies for failure to meet SLAs (service credits, termination right), benchmarking rights
    • Key Personnel — named key personnel (if applicable), replacement notice and approval requirements, non-solicitation of key personnel
    • Pricing and Payment Terms — fee structure (fixed, T&M, milestone-based), payment schedule and invoicing requirements, late payment terms, price escalation provisions, most-favored-customer clause (if applicable)
    • Expenses — reimbursable expense categories, pre-approval requirements and thresholds, documentation and receipting requirements
    • Change Order Process — procedure for requesting changes to scope, impact assessment requirements (cost, timeline, resources), written approval requirements, dispute resolution for change order disagreements
    • Confidentiality — mutual confidentiality obligations, definition of confidential information, permitted disclosures, return/destruction on termination
    • Data Protection Obligations — data processing agreement (if vendor processes personal data), data security standards and certifications, breach notification requirements and timelines, data handling restrictions (location, subprocessing), audit and inspection rights
    • Representations and Warranties — vendor authority and capacity, compliance with applicable laws, non-infringement of third-party IP, quality of services (professional standards, industry best practices), personnel qualifications and background checks
    • Indemnification — IP infringement indemnification, negligence and willful misconduct, data breach costs and liabilities, third-party claims arising from vendor's services, indemnification process and control of defense
    • Insurance Requirements — required coverage types (general liability, professional liability/E&O, cyber liability, workers' compensation), minimum coverage amounts, certificate of insurance requirements, additional insured status
    • Termination — termination for convenience (notice period, wind-down fees), termination for cause (cure period, material breach triggers), termination for insolvency, partial termination rights (individual SOWs)
    • Transition Assistance — vendor obligations during transition period, knowledge transfer requirements, cooperation with successor vendor, duration and cost of transition services
    • Limitation of Liability — aggregate liability cap (typically total fees under the agreement), exclusion of consequential damages, carve-outs (IP indemnification, confidentiality breach, data breach, willful misconduct, bodily injury)
    • Governing Law — choice of law, dispute resolution (escalation ladder: negotiation, mediation, arbitration/litigation), venue selection

Read the full file on GitHub · 63 lines

Changes

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.

  1. 3d ago First seen · 63 lines · 67 tokens per session scan A 20ed7017e125

Subscribe to this mod's changes

vendor-agreement is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 1,139 once invoked, about $0.0003 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.

Related

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…

cbrock84/headcount · 0 tokens

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…

cbrock84/headcount · 75 tokens

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…

cbrock84/headcount · 74 tokens

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…

cbrock84/headcount · 88 tokens

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.

fusengine/agents · 35 tokens

design-webapp

Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.

fusengine/agents · 31 tokens