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-coordinationgit 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-coordination)<a href="https://agentmods.dev/skills/quentincody/interlinked-cli/interlinked-coordination"><img src="https://agentmods.dev/badge/skills/quentincody/interlinked-cli/interlinked-coordination/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-coordination"><img src="https://agentmods.dev/badge/skills/quentincody/interlinked-cli/interlinked-coordination.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.00156 | $0.02932 |
| Opus 5.5 | $0.00062 | $0.01173 |
| Sonnet 5.5 | $0.00031 | $0.00586 |
| Haiku 4.5 | $0.00016 | $0.00293 |
Grade A, and why
interlinked-coordination 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 7d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
interlinked-coordination — multi-agent server surface & local checkpoints
The Interlinked CLI is a local companion; the Interlinked MCP Server is the source of truth for coordination. Two halves:
- Server-backed (needs auth + a reachable server):
tasks,send,inbox,handoff,workspace. These are thin wrappers that POST to the server; they do nothing useful offline (they short-circuit with "Not authenticated. Run: interlinked login"). (cloud recentalso needs a token but via a separatecloud_governor.url.attachis not server-gated — it writes config locally and only best-effort contacts the server, so it works offline.) - Local-only (offline):
checkpoint,rewind,resume,guard(git-hook reservation checks),reminder,ci-status,mcp stdio, and automatic file reservations among sibling agents on the same machine.
The whole server half is opt-in. Auth resolution: explicit --token → access_token in
config.local.json (auto-refresh) → Claude Code credentials fallback. localhost/127.0.0.1
server_url skips auth entirely (dev mode).
Load this when
- Picking up / handing off work, messaging a peer, or checking your inbox.
- A write was blocked/warned because a file is "reserved by" another agent.
- Switching workspace context.
- Creating or restoring a local checkpoint (read the git-safety warning first).
- Installing the git-hook reservation guard, or checking CI failure rates.
⚠️ Git-safety (read before any checkpoint/rewind/resume)
checkpoint, rewind, resume, and git link-checkpoint --apply mutate git state —
git stash, git checkout <sha> (detaches HEAD), git checkout -- . && git clean -fd
(discards uncommitted changes + deletes untracked files), or commit amend. Under the standing
rule that each commit/push/reset/stash/checkout is an independent per-turn ask, an agent
must not run these autonomously — describe and recommend, don't execute, unless the user
explicitly authorizes it this turn. Also note rewind rarely restores the working tree
(the checkpoint stash is popped at creation, so the message-based lookup usually finds nothing)
— its reliable effect is detaching HEAD to the base commit with a "changes may be missing"
warning. Don't rely on it as an undo.
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.
- 7d ago Changed · +8 lines 03637398b094
- 1mo ago Changed · +6 lines 53fe175bb6f5
- 1mo ago Changed · +16 lines 8f9c391a6914
- 1mo ago First seen · 142 lines · 156 tokens per session scan A 74dcdda8581b
interlinked-coordination is a skill published in the GitHub repository QuentinCody/interlinked-cli (180 stars, last pushed yesterday), licensed MIT. It adds 156 tokens to every session and 2,932 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.