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 DaizeDong/buy-me-a-car --skill close-day-checklistgit clone --depth 1 https://github.com/DaizeDong/buy-me-a-carWrote 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/daizedong/buy-me-a-car/close-day-checklist)<a href="https://agentmods.dev/skills/daizedong/buy-me-a-car/close-day-checklist"><img src="https://agentmods.dev/badge/skills/daizedong/buy-me-a-car/close-day-checklist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/daizedong/buy-me-a-car/close-day-checklist"><img src="https://agentmods.dev/badge/skills/daizedong/buy-me-a-car/close-day-checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00114 | $0.04539 |
| Opus 5 | $0.00057 | $0.02269 |
| Sonnet 5 | $0.00023 | $0.00908 |
| Haiku 4.5 | $0.00011 | $0.00454 |
Grade A, and why
close-day-checklist 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 12d 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close Day Checklist
Caveat: this skill is one author's playbook + 5-scenario stress test. Verify state fees / CPO terms / EV credits / dealer practices against current sources before quoting numbers to a dealer or making financial decisions. Not tax, legal, or financial advice. last_verified: 2026-05-18
Narrow sub-skill: buyer has a locked OTD in writing and is heading to the dealer to sign. No re-negotiation, no fresh outreach. For the full 9-phase workflow load ../orchestrator/SKILL.md; for upstream counter / follow-up drafting load dealer-reply-drafter.
When To Use
- Buyer is signing today or tomorrow and needs a sub-checklist by buyer type
- Buyer wants the F&I add-on refusal script to read verbatim at the F&I desk
- Buyer has a trade with active lien and needs the payoff workflow
- Buyer is an EV buyer and needs day-of EV mechanics (state rebate paperwork, battery/SoH, charging, NOTE: federal §30D POS credit transfer is TERMINATED 2025-09-30, historical only)
- Buyer is buying a pickup and needs the truck-specific PPI quick checklist
When NOT To Use
- OTD not yet locked in writing (use orchestrator Phase 6 /
dealer-reply-drafterfirst) - CARFAX not yet reviewed (use
carfax-pdf-reviewsub-skill) - PPI not yet booked (use
../orchestrator/references/ppi_booking.md) - Buyer wants to renegotiate at the F&I desk (don't - escalate per gotcha P3 F&I hard-no script)
Critical Rules Invoked
- Critical Rule #4: Read the actual CARFAX PDF yourself. Verbal "clean 1-owner" has a real failure rate. See gotcha V2. Re-confirm CARFAX was read end-to-end BEFORE close day.
- Critical Rule #1: Plain ASCII in every outbound email. Close-day GM heads-up email + F&I hard-no email must be ASCII only.
Close-Day Re-Confirmation (do this BEFORE buyer drives to dealer)
Re-read the close-day logistics mini-table from criteria.md and confirm each line:
- Bank cut-off + branch + hours (cashier's check issued same morning?)
- Insurance carrier (for binder + policy number)
- Plate decision (transfer existing vs new plates - saves $25-150 in most states)
- Available time windows on close day
- ID set (driver's license, secondary ID, proof of residence)
- Funding instrument (cash, cashier's check, wire, captive financing, CU financing)
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.
- 12d ago First seen · 311 lines · 114 tokens per session scan A be99565d455f
close-day-checklist is a skill published in the GitHub repository DaizeDong/buy-me-a-car (5 stars, last pushed 8d ago), licensed MIT. It adds 114 tokens to every session and 4,539 once invoked, about $0.0006 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
ideogram-ultra
Build Ideogram 4 (Ideogram Ultra) txt2img and img2img workflows with the local open-weights model, dual conditional/unconditional models with DualModelGuider, Qwen3-VL text encoder, and structured JSON ("compositional deconstruction") prompts for strong text rendering and layout control.
model-compatibility
Model family compatibility matrix covering loaders, resolutions, samplers, CFG, VAE, ControlNet, and LoRA compatibility for SD 1.5, SDXL, Flux, SD3, and video models.
flux-txt2img
Build Flux txt2img workflows with Flux.1 Dev (SRPO), Flux 2 Klein 9B, Turbo LoRAs, FluxGuidance, and DualCLIPLoader patterns.
panel-node-pack-sync
Keep the ComfyUI sidebar panel node-pack (comfyui-agent-panel) in step with the orchestrator after comfyui-mcp updates. Use this whenever the orchestrator was just updated (installcomfyui (action:"selfupdate"), npm i -g comfyui-mcp, a new version in the ENVIRONMENT line), when a panel/bridge command fails in a way…
civitai
Discover Civitai models with the BUILT-IN downloadmodel action:"searchcivitai" and install/generate them locally. Find a checkpoint/LoRA/embedding on Civitai, download it into ComfyUI, and use its trigger words. Optionally pair the official Civitai MCP for community features (images browsing, posting, collections).
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…