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 LawMotion-AI/Vibe-Lawyering --skill supplier-riskgit clone --depth 1 https://github.com/LawMotion-AI/Vibe-LawyeringWrote 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/lawmotion-ai/vibe-lawyering/supplier-risk)<a href="https://agentmods.dev/skills/lawmotion-ai/vibe-lawyering/supplier-risk"><img src="https://agentmods.dev/badge/skills/lawmotion-ai/vibe-lawyering/supplier-risk/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/lawmotion-ai/vibe-lawyering/supplier-risk"><img src="https://agentmods.dev/badge/skills/lawmotion-ai/vibe-lawyering/supplier-risk.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00187 | $0.03080 |
| Opus 5 | $0.00093 | $0.01540 |
| Sonnet 5 | $0.00037 | $0.00616 |
| Haiku 4.5 | $0.00019 | $0.00308 |
Grade A, and why
supplier-risk 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UNIVERSAL RULES (apply to every risk task)
- NEVER classify a sole-source supplier as low risk based on spend alone -- always assess operational dependency separately from spend volume
- NEVER accept a vendor risk assessment that contains fabricated financial data -- label all estimates and flag where primary data is unavailable
- ALWAYS flag when a vendor's Tier 2 sub-supplier shows distress signals that could affect Tier 1 supply continuity
- ALWAYS include specific recommended actions with deadlines in every output -- observations without actions are not acceptable
- FOR CHINESE SUPPLIERS: ALWAYS use QCC MCP as primary monitoring source -- real-time official data from SAMR, Courts, Tax authorities
- NEVER rely on Western data sources for Chinese entities -- Companies House, Creditsafe have ZERO coverage
MANDATORY OUTPUT HEADER
TASK: [e.g. Supplier Risk Brief -- Vendor X]
VENDOR TIER: [Strategic / Tactical / Commodity / Bottleneck / Unclassified]
CONFIGURATION: [Loaded: supply-chain.local.md / Not configured]
DATA SOURCES: [QCC MCP Risk Control / QCC MCP Enterprise / Web Search / ERP / Manual input]
QCC MCP RISK MONITORING (Chinese Suppliers)
Real-Time Risk Signal Monitoring (Supply Chain Focus)
QCC MCP provides continuous monitoring capabilities through 4 Server integration. Supply Chain Priority: Focus on signals that directly impact supply continuity.
| Risk Signal | QCC MCP Server | Supply Chain Impact | Alert Level | Response Time |
|---|---|---|---|---|
| SUPPLY INTERRUPTION HOT SIGNALS | ||||
| Bankruptcy filing | Risk Control | Immediate supply termination | 🔴 CRITICAL | < 4 hours |
| New dishonest被执行人 | Risk Control | Credit collapse, stop payment | 🔴 CRITICAL | < 24 hours |
| Environmental penalty (停产) | Risk Control | Production halt possible | 🔴 CRITICAL | < 24 hours |
| Major equity freeze | Enterprise Base | Control instability | 🔴 HIGH | < 48 hours |
| OPERATIONAL DISRUPTION SIGNALS | ||||
| Abnormal operation added | Enterprise Base | Regulatory intervention | 🔴 HIGH | < 48 hours |
| Serious violation | Enterprise Base | License revocation risk | 🔴 HIGH | < 48 hours |
| Cancellation filing | Enterprise Base | Intentional wind-down | 🔴 HIGH | < 48 hours |
| FINANCIAL STRESS SIGNALS | ||||
| Tax arrears announced | Risk Control | Cash flow crisis | 🟡 MEDIUM | < 7 days |
| Abnormal tax status | Risk Control | Compliance breakdown | 🟡 MEDIUM | < 7 days |
| Multiple equity pledges | Enterprise Base | Over-leverage | 🟡 MEDIUM | < 30 days |
| COMPLIANCE SIGNALS | ||||
| Administrative penalty | Risk Control | General compliance | 🟡 LOW | < 30 days |
| Environmental penalty (non-停产) | Risk Control | Fine only | 🟡 LOW | < 30 days |
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 · 302 lines · 187 tokens per session scan A df6dfdbf629a
supplier-risk is a skill published in the GitHub repository LawMotion-AI/Vibe-Lawyering (20 stars, last pushed 4mo ago), licensed MIT. It adds 187 tokens to every session and 3,080 once invoked, about $0.0009 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-30.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…