vendor-listing SKILL.md skillA
vendor-listing from superdesigndev/treg is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add superdesigndev/treg/vendor-listing@git:20261019.4df5b3fPins git:20261019.4df5b3f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- superdesigndev/treg
- Path
.agents/skills/vendor-listing/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261019.4df5b3f, committed Oct 19, 2026
- Size
- 18,832 bytes
- Repository stars
- 5,899
- License
- a license file GitHub does not identify
Onboard a vendor who wants their API listed in the treg catalog. Use whenever someone asks "how do we get listed on treg", a vendor sends their API details, or a listing PR/issue needs review. Walks the whole pipeline: eligibility gate → registry entry → platform-key slot → logo → tests → LIVE bogus-key test → core catalog YAML → verify → scrub → validate → evidence ledger in the PR. Every listing ships tier-4 wiring and a per-endpoint verification table. The vendor-facing doc this skill…
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 listing — add a provider to the catalog A listing has **three parts**, and all three ship in the same PR: 1. **Registry entry** (`src/treg/oauth_providers.py`) — how a team connects a credential for the provider, and how treg verifies that credential is real. 2. **Core catalog file** (`src/treg/catalog/<service>.yaml`) — what an agent can *do*: 8–15 curated endpoints with capability mapping, inputs, cost + provenance, and verified examples. 3. **Platform-key slot** (`config.py` + `fx.yaml`) — so treg can serve the endpoints on its own key (tier 4). **Always aim for this.** A listing that is BYOK-only is the exception and needs a stated reason (no self-serve pricing, `own_account` data, sales-gated). And every listing PR carries a **verification evidence ledger** (Step 7b). No ledger, no merge. Deep references (read before non-trivial work; do not duplicate them here): - `docs/context/guides/expanding-a-category.md` — the add-a-provider playbook, verify toolbox, traps - `docs/context/architecture/catalog.md` — catalog schema, cost provenance, verify pipeline, PII rules - `docs/VENDORS.md` — what we told the vendor to prepare (their checklist) …
Read the whole file at its exact version.
How to install
mdr add superdesigndev/treg/vendor-listing@sha256:9ca2404ac87652b1The line at the top of this page pins the label git:20261019.4df5b3f, 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_k24fqkufftikfaaf)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 19, 2026.
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 (18832 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
superdesigndev/treg · 5,899 stars · license a license file GitHub does not identify · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_k24fqkufftikfaaf GET https://markdownregistry.com/api/v1/resolve?ref=superdesigndev/treg/vendor-listing GET https://markdownregistry.com/api/v1/blob/9ca2404ac87652b175f893a6bd7832832bb11171f9d4eb44749e89d7cd9d6521
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.