vendor-management SKILL.md skillA
vendor-management from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/vendor-management@git:20260916.e72e404Pins git:20260916.e72e404 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/operations/skills/vendor-management/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260916.e72e404, committed Sep 16, 2026
- First version recorded
- Aug 28, 2026
- Size
- 3,564 bytes
- Repository stars
- 2,543
- License
- MIT
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or assess concentration and continuity risk.
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
# Vendor management ## Define requirements before looking at options Written before any demo: what the vendor must do, the volume and service level required, what must integrate with what, and the constraints that are genuinely non-negotiable. Requirements written after seeing a product describe that product. This is the most common way selections are decided before they are run. Separate **must-have** from **nice-to-have** and weight them in advance. Weighting after scoring is how a preferred vendor wins a process designed to be objective. ## Evaluating - **Reference checks with customers of your size and use case.** A reference running a tenth of your volume tells you nothing about whether it scales. - **Test the actual failure modes**, not the demo path. What happens when data is malformed, volume spikes, or an integration times out? - **Assess the vendor, not just the product** — financial stability, roadmap direction, support responsiveness, and whether you are a meaningful customer to them. Being a rounding error to your critical supplier is a risk in itself. - **Total cost including your side**: implementation, integration, migration, training, and the …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/vendor-management@sha256:0d8ae18ce7cb427fThe line at the top of this page pins the label git:20260916.e72e404, 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_hy6vwofnyhddnsvr)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 28, 2026 and Sep 16, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 3,564 B | A | view · diff |
| git:20260901.aa45383 | 2026-09-01 | aa45383 | 3,225 B | A | view · diff |
| git:20260828.f80dcb5 | 2026-08-28 | f80dcb5 | 2,854 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 (3564 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
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hy6vwofnyhddnsvr GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/vendor-management GET https://markdownregistry.com/api/v1/blob/0d8ae18ce7cb427fa711141dee5d82334982a8216c815c685f20bbaea816b86f
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.
More from cbrock84/headcount
Every file in cbrock84/headcount