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 agentmods add skills/cvander/maya/vendor_contactnpx skills add cvander/Maya --skill vendor_contactgit clone --depth 1 https://github.com/cvander/MayaWrote 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/cvander/maya/vendor_contact)<a href="https://agentmods.dev/skills/cvander/maya/vendor_contact"><img src="https://agentmods.dev/badge/skills/cvander/maya/vendor_contact.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00014 | $0.00440 |
| Opus 5 | $0.00007 | $0.00220 |
| Sonnet 5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
vendor-contact 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 5d 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.
What it actually says
Vendor Contact
Reads vendor docs and generates a contact draft (email body or phone script) for a specific vendor. Includes rep name, account number, and placeholder for order details.
Read-only. Does not modify files or reach external services. No PII in output.
When to Use
- When placing an order by email or phone
- After vendor-order generates the order text
- When contacting a vendor for the first time
Procedure
Run the skill from the repo root:
# Generate email draft
python -m skills.vendor_contact --vendor "Southern Glazer's" --method email --format json
# Generate phone script
python -m skills.vendor_contact --vendor "Anchor Distributing" --method phone --format json
Parse the JSON result:
status: "ok" (vendor not found) or "warn" (draft generated)data.message: the email body or phone script textdata.contact_info: vendor contact details (rep, phone, email)data.method: the contact method used
Exit Codes
| Code | Meaning |
|---|---|
| 0 | Vendor not found |
| 1 | Contact draft generated |
| 2 | Config error (bad arguments) |
| 3 | Data error (can't read vendor docs) |
| 10 | Unexpected error |
Verification
- Exit code is 0 or 1
- stdout is valid JSON (with --format json)
data.messageis non-empty when status is "warn"
What ships with it
10 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.
- __init__.py 65 B runs code
- __main__.py 422 B runs code
- fixtures/FIXTURES.md 207 B
- fixtures/happy_path/expected.json 748 B
- fixtures/happy_path/vendors.md 472 B
- fixtures/warn_case/expected.json 773 B
- fixtures/warn_case/vendors.md 472 B
- main.py 5.8 KB runs code
- manifest.toml 298 B
- test_main.py 4.3 KB runs code
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.
- 5d ago First seen · 67 lines · 14 tokens per session scan A ea4cd1cf07e5
vendor-contact is a skill published in the GitHub repository cvander/Maya (10 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 440 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…