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 QuentinCody/interlinked-cli --skill interlinked-coworkgit clone --depth 1 https://github.com/QuentinCody/interlinked-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/quentincody/interlinked-cli/interlinked-cowork)<a href="https://agentmods.dev/skills/quentincody/interlinked-cli/interlinked-cowork"><img src="https://agentmods.dev/badge/skills/quentincody/interlinked-cli/interlinked-cowork/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/quentincody/interlinked-cli/interlinked-cowork"><img src="https://agentmods.dev/badge/skills/quentincody/interlinked-cli/interlinked-cowork.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.00064 | $0.01280 |
| Opus 5.5 | $0.00026 | $0.00512 |
| Sonnet 5.5 | $0.00013 | $0.00256 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
interlinked-cowork 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 1mo 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interlinked Cowork
Cowork uses an uploaded plugin, separately from Claude Code settings. Ordinary Desktop Chat supports plugin skills but does not expose Cowork's hooks. Do not run enable --clients cowork; use interlinked cowork package --output <fresh-directory> and upload the resulting .plugin in Desktop Customize → Plugins. Requires the built standalone runtime, Node in the hook environment, and zip on the packaging host. After replacement, verify the displayed version/hooks and start a fresh task.
Native evidence and limitations
Run interlinked cowork capabilities --json. Dated native evidence is distinct from the current installation, which remains unmeasured until probed. On Desktop 1.49585.0 cloud mode, native deny, ask, input rewrite, and post-tool context were observed. Hook crashes and provider timeouts allowed synthetic writes. The guard launcher converts child failures, missing Node, and a 12-second internal deadline to explicit denial before the 15-second native deadline. If the provider never launches or kills the entire hook, this wrapper cannot enforce anything.
The ordinary plugin installs six lifecycle/tool hooks. A separate --probe package registers the larger Claude Code event catalog, including failure/subagent events, to measure availability; registration does not establish emission or enforcement. Keep fault injection confined to synthetic tasks, then disable the probe plugin. Do not retry denied actions through another tool.
Normal PostToolUse hooks match only Write, Edit, MultiEdit, NotebookEdit, Bash and the exact device Bash tool; reads/searches and unrelated connector tools do not trigger them. Probe subscriptions remain broad. Host guidance is encoded in PreToolUse additionalContext, including ordinary allows without a permission override; post-write artifact feedback is appended to host findings. Receipts still exclude guidance text. Pre-tool context delivery on the current native installation needs its own probe; local encoder tests are not native enforcement evidence.
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.
- 1mo ago First seen · 47 lines · 64 tokens per session scan A cdcecf4cea12
interlinked-cowork is a skill published in the GitHub repository QuentinCody/interlinked-cli (180 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 1,280 once invoked, about $0.0003 per session on Opus 5.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-14.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.