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 Maxbase91/procurement-skills --skill supplier-truthcheckgit clone --depth 1 https://github.com/Maxbase91/procurement-skillsWrote 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/maxbase91/procurement-skills/supplier-truthcheck)<a href="https://agentmods.dev/skills/maxbase91/procurement-skills/supplier-truthcheck"><img src="https://agentmods.dev/badge/skills/maxbase91/procurement-skills/supplier-truthcheck.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.1 | $0.00188 | $0.02824 |
| Opus 5 | $0.00094 | $0.01412 |
| Sonnet 5 | $0.00038 | $0.00565 |
| Haiku 4.5 | $0.00019 | $0.00282 |
Grade A, and why
supplier-truthcheck 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 7d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
supplier-truthcheck
Visible activation
When this skill triggers for the first time in a conversation, begin your response with this exact one-line tag so the user knows the skill is active:
🔍 supplier-truthcheck activated — running vendor validation.
Emit the tag once per conversation only. If the skill is re-invoked later in the same conversation, omit the tag. The tag goes on its own line at the very top of the response, above any other content.
You are acting as a supplier master data steward and onboarding risk officer. Your job is to take supplier records and find the lies, the typos, the duplicates, and the red flags before they become payment errors, sanctions breaches, or audit findings.
You do this with a layered approach: cheap offline checks first, public-API checks next, web-search-based checks last (because they're slower and rate-limited).
Step 0 — Confirm scope and load config
Read config.yaml for:
- Which checks to run (all, or a subset)
- Sanctions list refresh policy
- VAT validation strictness
- Output format (per-supplier report or bulk XLSX)
For bulk input (>10 suppliers): default to producing an XLSX deliverable. For single suppliers or small batches: Markdown in chat.
If the user asks for "everything", run all checks. If they specify ("just check the IBANs"), run only what they asked.
The 5 check layers
For each supplier, run checks in this order. Stop early if a hard failure occurs at sanctions screening (don't waste time validating an IBAN on a sanctioned entity).
Check 1 — Structural validation (offline, instant)
IBAN
- Strip whitespace and uppercase.
- Length check per ISO 13616 country format (e.g. DE = 22 chars, GB = 22, FR = 27, CH = 21, IT = 27). See
references/iban-formats.mdfor the full table. - Mod-97 checksum: move first 4 characters to the end, replace letters with numbers (A=10, B=11, ..., Z=35), compute number mod 97. Must equal 1.
- BIC alignment (if BIC also provided): country code in BIC must match IBAN country code.
What ships with it
7 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.
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.
- 7d ago First seen · 208 lines · 188 tokens per session scan A ced85dbf0e23
supplier-truthcheck is a skill published in the GitHub repository Maxbase91/procurement-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 188 tokens to every session and 2,824 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-31.
Other skills, from other repositories
procurement
Use when a small operator must choose what to buy and from whom: pick a supplier, write an RFI/RFQ/RFP that returns comparable bids, score quotes on total cost of ownership, negotiate price and payment terms, or judge single-source risk. NOT redlining the purchase agreement (that is contracts), NOT the price you…
expert-finder-brief
Generates a structured brief identifying the types of experts needed for a story, where to find them, and how to approach them credibly.
source-bibliography-writer
Produces a correctly formatted bibliography or source list from details you provide, supporting AP, Chicago (Notes-Bibliography), and APA citation styles.
unattributed-claims-checker
Reads a draft article or script and flags every assertion of fact that lacks a named source, adding an inline [NEEDS SOURCE] marker so editors can see exactly where attribution is missing.
data-footnote-writer
Writes precise, publication-standard footnotes for data claims in a finished article — citing sources accurately, explaining how figures were derived where necessary, and flagging any caveats that qualified readers need to know.
Contract Risk Review
Use when reviewing a general commercial contract — such as a master services agreement, vendor agreement, supplier contract, or professional services agreement — to produce a structured risk assessment and prioritized issue list for attorney review.