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 CALLE-AI/awesome-phone-call-agents --skill supply-chain-supplier-statusgit clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agentsWrote 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/calle-ai/awesome-phone-call-agents/supply-chain-supplier-status)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/supply-chain-supplier-status"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/supply-chain-supplier-status/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/calle-ai/awesome-phone-call-agents/supply-chain-supplier-status"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/supply-chain-supplier-status.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.00041 | $0.02197 |
| Opus 5.5 | $0.00016 | $0.00879 |
| Sonnet 5.5 | $0.00008 | $0.00439 |
| Haiku 4.5 | $0.00004 | $0.00220 |
Grade A, and why
supply-chain-supplier-status 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supply Chain Supplier Status Check
Purpose And When To Use
Use this skill when an enterprise procurement or supply chain operations team needs to verify upcoming purchase order fulfillment with authorized suppliers, detect delivery slippages before factory or warehouse stockouts occur, and capture structured delay intelligence.
This is the portable skill specification for Supply Chain Supplier Status Agent, providing the structured conversational inquiry tree, CALL-E API dispatch contract, and procurement intelligence schemas.
Use this skill for:
- proactive order verification calls to authorized vendor dispatchers
- capturing delivery schedule slips and delay root cause categories
- recording revised delivery dates and expedited freight commitments
- quantifying delay penalty exposure and recording supervisor escalation details
- generating structured procurement dashboards and ERP-compatible records
When Not To Use
Do not use this skill to:
- place unsolicited cold calls to numbers without an established vendor relationship or purchase order reference
- negotiate binding contract amendments, pricing changes, or warranty releases without human authorization
- cancel purchase orders, terminate supplier contracts, or initiate legal action
- record payment credentials, banking details, or sensitive personal data
- initiate unauthorized automated calls outside business hours or without recording consent where required by law
- retry endlessly when a vendor contact declines or requests human follow-up
- any workflow requiring in-flight call cancellation after dispatch (the CALL-E Calls API has no cancel endpoint; keep waves small)
Required Inputs
Before initiating a call, ensure the following fields are provided:
supplier_id: Unique identifier for the vendor (e.g.,SUP-101)supplier_name: Commercial legal entity namephone_number: Authorized E.164 phone number (^\+[1-9]\d{6,14}$, e.g.,+15550149923)purchase_order_id: Associated active purchase order identifier (e.g.,PO-88120)scheduled_delivery_date: Committed fulfillment deadline (YYYY-MM-DD)company_name: Disclosed enterprise caller identityauthorization_confirmed: Explicit operator confirmation (true) that the call and specific recipient are authorizeddestination_authorized: Explicit operator attestation (true) that the destination phone number matches the supplier's verified dispatch contact on file
What ships with it
3 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.
- 1mo ago First seen · 173 lines · 41 tokens per session scan A 6894fba05031
supply-chain-supplier-status is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 2,197 once invoked, about $0.0002 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-15.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…