What is interlinked-verify?

A verification skill for Interlinked, a local system that checks coding-agent changes for policy, quality, and project consistency.

Use it to verify a batch of edits, inspect post-edit checks, or land multi-file changes through Interlinked's content gates.

It lets you run the project's checks on demand and understand or resolve warnings and blocked edits before finishing a change.

interlinked-verify — Skill by QuentinCody

Install

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.

agentmods

npx agentmods add skills/quentincody/interlinked-cli/interlinked-verify

Any agent

npx skills add QuentinCody/interlinked-cli --skill interlinked-verify

Clone the repo

git clone --depth 1 https://github.com/QuentinCody/interlinked-cli

Made for: Claude Code, Codex.

Per session 158 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,538 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00158	$0.03538
Opus 5	$0.00079	$0.01769
Sonnet 5	$0.00032	$0.00708
Haiku 4.5	$0.00016	$0.00354

Measured 2d ago against content hash 9d06375ffa0e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

interlinked-verify 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 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.

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.

skills/interlinked-verify/SKILL.md · 209 lines

How it starts

The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.

interlinked-verify — check your work & land edits through the gates

Interlinked gates edits at three moments, and they run different check sets:

PreToolUse content gate (real Edit/Write, and interlinked write/verify-changeset): runs pre_block registry checks → biome overlay → tsc overlay. Blocking findings stop the write. No coverage/complexity/post checks here. (interlinked multi-edit is the exception — it runs only biome + tsc, not pre_block; see the ordering section.)
Other PreToolUse guards (real Edit/Write only): coverage, cyclomatic, CRAP, baseline — see interlinked-quality-gates; package/allowlist — see interlinked-supply-chain.
PostToolUse (after the write lands): external tools (tsc/biome/eslint/semgrep/gitleaks/…) plus the inline check registry. Warn only — surfaced to you next turn. Bash and unknown writer tools are routed by their observed filesystem ChangeSet, not merely command parsing.

interlinked verify is the on-demand, whole-project run of that same check catalog.

Load this when

You want to verify a batch of edits before declaring done.
A pre_block check blocked an edit (see also interlinked-harness for how blocks read).
You're landing a cross-file refactor and hitting transient tsc errors.
You're unsure whether a finding is default-gate or advisory-only.
You need to write a probe/analysis script and want it in the right place.

`interlinked verify`

interlinked verify [target]
  --all-checks        add the advisory smell/complexity/dead-code tier to the default gate
  --only <tool>       run only one external tool (e.g. --only tsc)
  --skip <ids>        comma-separated check ids to skip
  --suggestions       also run scored regex heuristics (sql-injection/perf/quality)
  --structure         also run artifact-structure checks
  --adoption-gate     fail when adopted structure categories drop below thresholds
  --suppress <e...>   add a suppression (file:check or file:check:reason)
  --json --details    machine-readable / per-file detail

target may be a local path, a GitHub/git URL (cloned to a tmpdir, scanned, deleted), or omitted (scans cwd). Narrow with --subdir <path> in monorepos.

Read the full file on GitHub · 209 lines

Files

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.

agents/openai.yaml 259 B

Changes

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 · 209 lines · 158 tokens per session scan A 9d06375ffa0e

Subscribe to this mod's changes

interlinked-verify is a skill published in the GitHub repository QuentinCody/interlinked-cli (13 stars, last pushed 15d ago), licensed MIT. It adds 158 tokens to every session and 3,538 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.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens