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-harnessnpx skills add QuentinCody/interlinked-cli --skill interlinked-harnessgit 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.00151 | $0.03701 |
| Opus 5 | $0.00076 | $0.01851 |
| Sonnet 5 | $0.00030 | $0.00740 |
| Haiku 4.5 | $0.00015 | $0.00370 |
Grade D, and why
interlinked-harness scanned grade D with 3 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| **Destructive fs** | `rm -rf /`, `rm -rf *`, `rm node_modules`, `sudo rm …`, `dd`, `mkfs`, `shred`, `chmod 777` | `rm -rf /tmp/x`, `rm -rf dist/`, `rm -rf .wrangler/cache` | Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
quoted/heredoc/comment text, so *mentioning* `rm -rf /` in an `echo` is allowed while the Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| **Info-flow / persistence** | env exfil (`env \| curl …`, `printenv \| nc …`), `.npmrc`/`.yarnrc` writes, `nohup curl … &`, `crontab -e`, `systemctl enable`, writes to `/etc/cron.d/`, `*.service` | — | How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
interlinked-harness — the guard: what blocks you & how to respond
Interlinked runs a local daemon that evaluates every agent tool call before it runs (PreToolUse). It is default-permit with targeted forbid: it allows everything except known-dangerous shapes, which it refuses with an actionable reason and a safer alternative. It is a fast deterministic guardrail, not a security trust boundary (it's local and bypassable) — so the right instinct when blocked is to take the suggested safe path, not to defeat the pattern.
Load this when
- A tool call was refused:
BLOCKED: <reason>/Suggestion: <safer alternative>. - You see an
[interlinked:<check>]warning (tagged[proven]or[heuristic]). - A destructive command,
git push --force, protected-file, secret, repo-confinement, or bash-redirect-bypass rule fired. - You need to legitimately suppress a check false-positive, or disable a wrong guard rule.
Mental model
- A hook ships each tool call to the daemon over a Unix socket. The daemon runs an ordered set of phases; the first phase that returns a terminal decision wins.
- Decisions:
block(tool refused, you see the reason),ask(human confirmation — on runners without an ask primitive, like Codex/Copilot/Gemini, ask downgrades to deny), orallow(may still carry non-blockingwarnings, or anupdated_inputrewrite). - Built-in rules are regex patterns on the command/tool-input. Use
interlinked harness checksfor the authoritative current inventory. Patterns are ORed over positive entries;negate:truepatterns are exceptions.executed_onlymasks quoted/heredoc/comment text, so mentioningrm -rf /in anechois allowed while the bare command blocks. Compound commands (&&,||,;,|, newline) are decomposed and each part checked.
Two unrelated things are called "guard". This skill is the PreToolUse guard (the daemon, operated via
interlinked harness …).interlinked guardis a separate git pre-commit/pre-push hook that checks staged files against file reservations — see interlinked-coordination.
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.
- 2d ago First seen · 192 lines · 151 tokens per session scan D 44962653fdd3
interlinked-harness is a skill published in the GitHub repository QuentinCody/interlinked-cli (13 stars, last pushed 14d ago), licensed MIT. It adds 151 tokens to every session and 3,701 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, recursive force delete, makes network calls). 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.