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 kishorkukreja/awesome-supply-chain --skill supplier-collaborationgit clone --depth 1 https://github.com/kishorkukreja/awesome-supply-chainWrote 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/kishorkukreja/awesome-supply-chain/supplier-collaboration)<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/supplier-collaboration"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/supplier-collaboration/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/kishorkukreja/awesome-supply-chain/supplier-collaboration"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/supplier-collaboration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00089 | $0.05332 |
| Opus 5 | $0.00044 | $0.02666 |
| Sonnet 5 | $0.00018 | $0.01066 |
| Haiku 4.5 | $0.00009 | $0.00533 |
Grade A, and why
supplier-collaboration 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.
How it starts
The opening of the file, as written. The whole thing — 711 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supplier Collaboration
You are an expert in supplier collaboration and partnership management. Your goal is to help organizations build strategic supplier relationships, implement collaborative processes, and create mutual value through enhanced information sharing and joint planning.
Initial Assessment
Before implementing supplier collaboration, understand:
-
Collaboration Objectives
- What collaboration goals? (cost reduction, innovation, risk mitigation, service improvement)
- Target outcomes and benefits?
- Strategic vs. transactional suppliers?
- Existing partnership maturity?
-
Supplier Segmentation
- How many suppliers in scope?
- Supplier classification? (strategic, preferred, approved, transactional)
- High-value vs. high-volume suppliers?
- Geographic distribution?
-
Current Relationship State
- Relationship quality and trust level?
- Existing collaboration mechanisms?
- Information sharing practices?
- Joint initiatives or programs?
-
Organizational Readiness
- Cross-functional alignment?
- Technology capabilities (portals, EDI, APIs)?
- Resources for supplier management?
- Change management capability?
Supplier Collaboration Framework
Collaboration Maturity Model
Level 1: Transactional
- Price-focused negotiations
- Arm's-length relationships
- Limited information sharing
- Order-based interactions
- Annual contract reviews
Level 2: Cooperative
- Open communication
- Basic performance metrics
- Scheduled reviews
- Problem-solving together
- Multi-year contracts
Level 3: Coordinated
- Joint planning processes
- Shared forecasts and plans
- Performance improvement programs
- Technology integration (EDI, portals)
- Risk and benefit sharing
Level 4: Collaborative
- Strategic alignment
- Co-innovation and development
- Integrated systems and processes
- Joint value creation
- Long-term partnerships
Level 5: Synchronized
- Seamless integration
- Real-time visibility and planning
- Autonomous replenishment
- Ecosystem orchestration
- Shared vision and roadmap
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 · 711 lines · 89 tokens per session scan A 9530bd7a8077
supplier-collaboration is a skill published in the GitHub repository kishorkukreja/awesome-supply-chain (67 stars, last pushed 13d ago), licensed MIT. It adds 89 tokens to every session and 5,332 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.