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 charlieviettq/awesome-agent-skill --skill biz-supply-chaingit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/biz-supply-chain)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/biz-supply-chain"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/biz-supply-chain/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/charlieviettq/awesome-agent-skill/biz-supply-chain"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/biz-supply-chain.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.00088 | $0.01327 |
| Opus 5 | $0.00044 | $0.00664 |
| Sonnet 5 | $0.00018 | $0.00265 |
| Haiku 4.5 | $0.00009 | $0.00133 |
Grade A, and why
"biz-supply-chain" 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 9d 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.
This is a copy
92% identical to biz-supply-chain — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supply Chain Analysis (SCOR Model)
Overview
The SCOR (Supply Chain Operations Reference) model structures supply chain analysis into five core processes: Plan, Source, Make, Deliver, Return. It provides a common language for analyzing, benchmarking, and improving supply chain performance from supplier's supplier to customer's customer.
Framework
IRON LAW: End-to-End, Not Silo-by-Silo
Supply chain optimization must consider the ENTIRE chain. Optimizing
procurement (Source) without considering production capacity (Make) or
delivery capability (Deliver) creates bottlenecks downstream.
A local optimum in one process often creates a global problem elsewhere.
The Five SCOR Processes
1. Plan — Demand forecasting, supply planning, inventory strategy
- Demand forecast accuracy, S&OP process, inventory policies
- Question: "Do we make/buy the right amount at the right time?"
2. Source — Supplier selection, procurement, incoming quality
- Supplier scorecards, lead times, sourcing strategy (single vs multi)
- Question: "Are we getting the right inputs at the right cost and quality?"
3. Make — Production, assembly, manufacturing
- Production scheduling, capacity utilization, quality control, WIP management
- Question: "Are we converting inputs to outputs efficiently?"
4. Deliver — Order management, warehousing, transportation, last-mile
- Order fulfillment rate, delivery speed, logistics cost, channel management
- Question: "Are we getting products to customers reliably and affordably?"
5. Return — Returns processing, reverse logistics, warranty/repair
- Return rate, reverse logistics cost, refurbishment, disposal
- Question: "Are we handling returns efficiently and learning from them?"
Key Supply Chain Metrics
| Process | Metric | Formula/Definition |
|---|---|---|
| Plan | Forecast Accuracy | 1 - |Actual - Forecast| / Actual |
| Plan | Inventory Days | Inventory / (COGS / 365) |
| Source | Supplier On-Time Rate | On-time deliveries / Total deliveries |
| Source | Supplier Defect Rate | Defective units / Total received |
| Make | OEE | Availability × Performance × Quality |
| Deliver | Perfect Order Rate | Orders delivered on time, in full, without error |
| Deliver | Order-to-Delivery Cycle | Time from order to customer receipt |
| Return | Return Rate | Returns / Total shipments |
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.
- 9d ago First seen · 121 lines · 88 tokens per session scan A 1b7473950db5
"biz-supply-chain" is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (26 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 1,327 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to biz-supply-chain, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
punch-list-manager
Digital punch list management for construction project closeout. Track deficiencies, assign corrections, photo documentation, and completion verification.
safety-inspection
Digital safety inspection system for construction sites. Checklists, hazard tracking, incident reporting, and compliance documentation.
data-evolution-analysis
Analyze data evolution patterns in construction organizations. Assess digital maturity and data strategy for construction companies.
data-silo-detection
Detect and map data silos in construction organizations. Identify disconnected data sources and integration opportunities.