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 jeffreytse/grimoire-core --skill design-vendor-risk-assessmentgit clone --depth 1 https://github.com/jeffreytse/grimoire-coreWrote 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/jeffreytse/grimoire-core/design-vendor-risk-assessment)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-vendor-risk-assessment"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-vendor-risk-assessment/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/jeffreytse/grimoire-core/design-vendor-risk-assessment"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-vendor-risk-assessment.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.00067 | $0.01501 |
| Opus 5.5 | $0.00027 | $0.00600 |
| Sonnet 5.5 | $0.00013 | $0.00300 |
| Haiku 4.5 | $0.00007 | $0.00150 |
Grade A, and why
design-vendor-risk-assessment 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 1mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Vendor Risk Assessment
Establish an ongoing program to assess and monitor a critical third-party vendor's operational, security, financial, and compliance risk — rather than evaluating the vendor once at contract signing and never revisiting the assessment, even as the vendor relationship, the vendor's own condition, and the organization's dependence on it all evolve over time.
Why This Is Best Practice
Adopted by: NIST Special Publication 800-161, "Cybersecurity Supply Chain Risk Management Practices," documents structured vendor and supply-chain risk assessment as a required discipline for organizations managing third-party dependencies, and ongoing vendor risk management (VRM) programs — as distinct from one-time vendor due diligence — are standard practice across procurement, security, and operational risk functions in organizations that depend on critical third-party vendors. Impact: A vendor assessed as low-risk at the point of contract signing can become significantly riskier over time — its financial condition can deteriorate, its security practices can weaken, its compliance posture can lapse, or the organization's own dependence on it can deepen — and an organization that only assessed the vendor once, at signing, has no mechanism to detect this drift before it results in an actual disruption or failure. Why best: A one-time vendor evaluation captures only a snapshot of the vendor's risk profile at a single point in time, while the actual risk the organization bears from the relationship accumulates and changes continuously over the life of the engagement — an ongoing monitoring program is specifically designed to detect this drift, providing warning and time to react before a vendor's deteriorating condition results in an actual failure affecting the organization.
Sources: NIST Special Publication 800-161, "Cybersecurity Supply Chain Risk Management Practices"; standard vendor/third-party risk management (VRM) industry practice
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.
- 1mo ago First seen · 68 lines · 67 tokens per session scan A 5c8ad4fd9fba
design-vendor-risk-assessment is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 67 tokens to every session and 1,501 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
counseling-psychology
Therapeutic frameworks, assessment, ethical practice, and client documentation for counselors and psychologists.
semantic-model-disambiguation
Analyze Power BI semantic models for column-level overlaps that confuse Copilot and Fabric data agents. Detect ambiguity, review with domain expert, apply fixes via MCP.
prompt-2-data
Generate comprehensive synthetic relational data for any specified subject with multiple normalized CSV files maintaining referential integrity.
academic-paper-drafting
End-to-end academic paper drafting for CHI, HBR, journals, and conferences with venue-specific templates, drafting workflows, and revision strategies.
research-first-development
Build knowledge bases that build software — research before code, teach before execute.
infrastructure-as-code
Domain: DevOps & Cloud Engineering.