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 agentmods add skills/drvoss/everything-copilot-cli/agent-supply-chainnpx skills add drvoss/everything-copilot-cli --skill agent-supply-chaingit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWrote 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/drvoss/everything-copilot-cli/agent-supply-chain)<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/agent-supply-chain"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/agent-supply-chain.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 | $0.00051 | $0.04145 |
| Opus 5 | $0.00026 | $0.02073 |
| Sonnet 5 | $0.00010 | $0.00829 |
| Haiku 4.5 | $0.00005 | $0.00415 |
Grade A, and why
agent-supply-chain scanned grade A with 2 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 today.
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.
Reads MCP configurationlowAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
git --no-pager grep -n "@latest" -- ".mcp.json" "*.json" "*.yaml" "*.yml" Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
git --no-pager grep --no-index -E -n "base64.*(curl|Invoke-WebRequest|fetch\()" -- $root How it starts
The opening of the file, as written. The whole thing — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Supply Chain
Verify that agent plugins, skill bundles, and MCP packages have not drifted between review, testing, and deployment.
When to Use
- Before promoting an agent plugin or MCP bundle from dev to staging or production
- When reviewing third-party skills, plugins, or local MCP servers before adoption
- When a repository needs deterministic integrity evidence instead of "looks unchanged"
- When dependency pinning and manifest checks should become part of a release gate
When NOT to Use
| Instead of agent-supply-chain | Use |
|---|---|
| Generic codebase vulnerability review | security-scan |
| Repository-wide trust scoring and hygiene review | evaluate-repository |
| GitHub Actions workflow exploit review | gha-security-review |
Workflow
1. Define the review boundary
Decide exactly what should be covered by the integrity check:
- the plugin or skill directory itself
- its manifest files
- related config such as
.mcp.json,package.json,requirements.txt - any local action or helper scripts that ship with the package
Exclude generated artifacts and cache directories so the manifest stays deterministic.
2. Generate a deterministic manifest
Create an INTEGRITY.json file with SHA-256 hashes for every tracked source file.
$root = "path\\to\\plugin"
$excludeDirs = @(".git", "node_modules", "__pycache__", ".venv", ".pytest_cache")
$excludeFiles = @("INTEGRITY.json", ".DS_Store", "Thumbs.db")
$files = Get-ChildItem -Path $root -Recurse -File |
Where-Object {
$relative = $_.FullName.Substring((Resolve-Path $root).Path.Length + 1)
-not ($excludeFiles -contains $_.Name) -and
-not ($excludeDirs | Where-Object { ($relative -split '[\\/]') -contains $_ })
} |
Sort-Object FullName
$manifestFiles = @{}
foreach ($file in $files) {
$relative = $file.FullName.Substring((Resolve-Path $root).Path.Length + 1).Replace('\', '/')
$hash = (Get-FileHash -Algorithm SHA256 -LiteralPath $file.FullName).Hash.ToLower()
$manifestFiles[$relative] = $hash
}
$chain = [System.Security.Cryptography.SHA256]::Create()
$joined = ($manifestFiles.Keys | Sort-Object | ForEach-Object { $manifestFiles[$_] }) -join ""
$manifestHash = [Convert]::ToHexString($chain.ComputeHash([System.Text.Encoding]::UTF8.GetBytes($joined))).ToLower()
$manifest = [ordered]@{
plugin_name = Split-Path $root -Leaf
generated_at = (Get-Date).ToUniversalTime().ToString("o")
algorithm = "sha256"
file_count = $manifestFiles.Count
files = $manifestFiles
manifest_hash = $manifestHash
}
$manifest | ConvertTo-Json -Depth 5 | Set-Content -LiteralPath (Join-Path $root "INTEGRITY.json")
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.
- today First seen · 387 lines · 51 tokens per session scan A b532ca7ee109
agent-supply-chain is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 8d ago), licensed MIT. It adds 51 tokens to every session and 4,145 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 2 findings (reads mcp configuration, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
winui-design
Use when designing, reviewing, or fixing WinUI 3: sample and control discovery with winapp find-ui, layout planning, control choice, Fluent Design alignment, Light/Dark/High Contrast theming, typography, spacing, brushes, accessibility, and XAML data-binding design. Load before authoring new XAML, reviewing UI PRs…
winui-dev-workflow
Build and run workflow for WinUI 3 apps with WinApp CLI 0.6+ — project creation with winapp new, project-mode winapp run, BuildAndRun.ps1 analyzer integration, crash diagnosis, and prerequisites. Use when creating, building, running, or fixing build errors in a WinUI 3 project.
winui-packaging
MSIX packaging, code signing, and distribution for WinUI 3 apps — build for release, certificate generation (winapp cert generate), certificate trust, code signing (winapp sign), self-contained deployment, CI/CD with GitHub Actions, and Microsoft Store submission. Use when preparing for release, creating MSIX…
winui-session-report
Analyze the current or a recent agent session (GitHub Copilot CLI or Claude Code) and generate a diagnostic report. Use only when the user explicitly asks for session feedback, agent debugging, or a review of what happened during a build session. Do not inspect session data automatically.
microsoft-build
Your companion for Microsoft Build 2026. Helps you find sessions relevant to your project, discover what's new for your tech stack, scaffold projects from sessions, and plan your event schedule. Activate when users mention sessions, schedule, what's new, Build, Ignite, AI Tour, Microsoft event, conference, or…
journey-template
Create new agentic journeys from app ideas. Generates README.md (learner walkthrough), PLAN.md (AI-readable spec), and app-specific skills for OSS deployments. Supports any stack (Node.js, Python, .NET, Java, Swift, Kotlin) and Azure service (Container Apps, AKS, Functions, App Service). USE FOR: new journey, scaffold…