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 LeadMagic/gtm-skills --skill vendor-contractsgit clone --depth 1 https://github.com/LeadMagic/gtm-skillsWrote 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/leadmagic/gtm-skills/vendor-contracts)<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/vendor-contracts"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/vendor-contracts.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 263 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00109 | $0.03125 |
| Opus 5 | $0.00055 | $0.01563 |
| Sonnet 5 | $0.00022 | $0.00625 |
| Haiku 4.5 | $0.00011 | $0.00313 |
Grade A, and why
vendor-contracts 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 4d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vendor Contracts & Procurement
Overview
Contracts are the skeleton of enterprise sales. A clean MSA + Order Form + DPA + SLA package closes deals in weeks. A messy, non-standard contract gets stuck in legal review for months. The mistake: letting every enterprise customer dictate terms from scratch. You need standard templates that cover 80% of deals, with red-line boundaries for the remaining 20%. This skill covers the complete contract stack: MSA, Order Form, SLA, DPA — for both selling to customers (inbound) and buying from vendors (outbound).
Authoritative Foundations
- YC — Standard commercial terms for B2B SaaS — Startup operating cadence — default alive, talk to users, launch fast.
- SaaS Capital — B2B SaaS contract benchmarks — B2B SaaS contract benchmarks
- Jason Lemkin (SaaStr) — Enterprise contract negotiation — Enterprise contract negotiation
- David Skok (Matrix Partners) — B2B contract structure — SaaS metrics — CAC payback, LTV/CAC, unit economics by stage.
When to Use
Trigger phrases: "MSA template", "master service agreement", "order form", "SLA agreement", "data processing agreement template", "enterprise contract", "vendor contract", "procurement process", "contract negotiation", "commercial terms for SaaS", "standard contract"
Step-by-Step Process
Phase 1: Inbound Contracts (Selling to Customers)
The standard contract stack:
CONTRACT STACK (4 documents):
1. MSA (Master Services Agreement)
- The "umbrella" contract. Signed once. Governs the entire relationship.
- Covers: service description, payment terms, term/termination, IP,
confidentiality, limitation of liability, warranties, indemnification,
governing law, dispute resolution
2. Order Form
- Each purchase gets its own Order Form.
- Covers: products purchased, quantity (seats/volume), price, term length,
billing frequency, renewal terms, special terms
- References the MSA
3. SLA (Service Level Agreement)
- Can be part of MSA or separate.
- Covers: uptime commitment, response times, credits for downtime,
support hours, escalation paths
4. DPA (Data Processing Agreement)
- Required for GDPR compliance and enterprise deals.
- Covers: data processed, purpose, sub-processors, security measures,
breach notification, data subject rights, SCCs
What ships with it
3 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.
- 4d ago First seen · 289 lines · 109 tokens per session scan A 0e43fa681d65
vendor-contracts is a skill published in the GitHub repository LeadMagic/gtm-skills (48 stars, last pushed yesterday), licensed MIT. It adds 109 tokens to every session and 3,125 once invoked, about $0.0005 per session on Opus 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-09-03.
Other skills, from other repositories
huashu-takram-soft-tech
OpenDesign procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.
crisis-holding
Draft crisis holding statements, journalist Q&A posture, and what-not-to-say guidance from confirmed incident facts, with a hard legal-counsel gate. Builds each statement through proven crisis-comms frameworks (holding-statement anatomy, SCCT, CAP order, the legitimate non-answer, bridge/flag/block).
startup-launch-playbook
A step-by-step playbook for early-stage startups going from pre-seed to their first 1000 users. Covers MVP validation, initial traction channels, and founder-led growth tactics. By @WeiYipei — follow on X for more startup growth insights.
cialdini-influence
Applies Cialdini's seven principles of ethical persuasion -- Reciprocity, Commitment and Consistency, Social Proof, Authority, Liking, Scarcity, and Unity -- to business contexts including sales, marketing, fundraising, and negotiation. Use when designing conversion funnels, optimizing sales processes, preparing…
competitor-monitoring
Use this skill when you need to know what rival companies are doing — "what are my competitors doing", "competitor update", "competitor news", "competitive landscape", "market intel", "what's new with [company]", "track [company]", "competitor briefing", "who's making moves", "we keep losing deals to [company]" — or…
multichannel-campaign-builder
Use this skill when someone needs a complete outbound sequence written — every touch across LinkedIn and email, not a single cold email. Produces three distinct angles to choose from, then the full sequence with each message ready to send, calibrated to the campaign type and channel mix and self-checked against a…