gtm-spend-management SKILL.md skillA
gtm-spend-management from leadmagic/gtm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add leadmagic/gtm-skills/gtm-spend-management@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- leadmagic/gtm-skills
- Path
skills/gtm-ops/gtm-spend-management/SKILL.md- Versions recorded
- 6
- Latest version
- v1.1.0, committed Oct 1, 2026
- First version recorded
- Jun 10, 2026
- Size
- 10,172 bytes
- Repository stars
- 76
- License
- MIT
GTM spend management — Ramp corporate cards, virtual cards per vendor, SaaS vendor roster, tool spend approvals, bill pay, accounting sync, and shadow-IT cleanup. Use when setting up Ramp, governing GTM tool purchases, tracking vendor renewals, or controlling per-rep software spend. Triggers on: "spend management", "Ramp setup", "corporate card GTM", "vendor spend", "SaaS spend governance", "tool purchase approval", "virtual card per vendor", "Brex vs Ramp", "zombie subscriptions…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# GTM Spend Management ## Overview GTM tool spend leaks through **personal cards**, **auto-renewals nobody owns**, and **one-off trials that become $800/mo**. Finance sees a Ramp statement; RevOps sees 40 SaaS logos — neither has a **vendor roster** with owner, renewal date, and cost per rep. The mistake: modeling TCO in a spreadsheet while purchases bypass approval entirely. This skill operationalizes spend: **Ramp** (or equivalent) for cards + bill pay, **approval matrix** by dollar tier, **virtual card per vendor** for GTM tools, and a living **vendor spend register** synced to `gtm-tool-cost-model`. TCO math → `gtm-tool-cost-model`. Contract terms → `vendor-contracts`. Stack audit → `revops-tech-stack`. **Annual GTM budget (canonical opEx home):** `references/gtm-budget-playbook.md` — this skill owns **vendor/tool lines** inside that budget. ## When to Use - "Set up Ramp for GTM tools" - "Who approves new SaaS purchases?" - "Track vendor renewals and spend" - "Virtual card for Clay / Gong / HubSpot" - "Clean up zombie subscriptions" - "GTM spend governance policy" - "Brex vs Ramp for startup" - "Bill pay for annual SaaS renewals" ## Authoritative Foundations …
Read the whole file at its exact version.
How to install
mdr add leadmagic/gtm-skills/gtm-spend-management@sha256:ba4d6fb39632f346The line at the top of this page pins the label v1.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_slbrerriq5gswfn7)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 10, 2026 and Oct 1, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-10-01 | ca0d2ec | 10,172 B | A | view · diff |
| v1.1.0 | 2026-09-02 | a19750a | 10,190 B | A | view · diff |
| v1.1.0 | 2026-06-10 | e030e67 | 10,184 B | A | view · diff |
| v1.1.0 | 2026-06-10 | 0173be3 | 10,184 B | A | view · diff |
| v1.1.0 | 2026-06-10 | 17b6e1f | 10,207 B | A | view · diff |
| v1.1.0 | 2026-06-10 | 9f00d65 | 10,208 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10172 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
leadmagic/gtm-skills · 76 stars · license MIT · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_slbrerriq5gswfn7 GET https://markdownregistry.com/api/v1/resolve?ref=leadmagic/gtm-skills/gtm-spend-management GET https://markdownregistry.com/api/v1/blob/ba4d6fb39632f346fb2d38f8f6ce8e577b3f7bab35a16162951d6b6eec54b2bc
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.